Link directly to PDF version?

I'd like to be able to give users a link that will take them directly to
the PDF version of a report without ever seeing the interactive reports
server pages or having to use the export command manually. The PDF would
have to be freshly generated each time, rather than simply linking to
the PDF output from a subscription delivery.
Is this possible?Yes by using the Format command set to PDF, e.g.:
http://servername/reportserver?/SampleReports/Company
Sales&rs:Format=PDF&rs:Command=Render
If you want to avoid report session caching and generate the report anew
with each user requests, append rs:ClearSession=true to the URL link.
--
Hope this helps.
---
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
http://www.prologika.com
"JC Ford" <johncford@.hotmail.com> wrote in message
news:OGb6H15fEHA.1048@.tk2msftngp13.phx.gbl...
> I'd like to be able to give users a link that will take them directly to
> the PDF version of a report without ever seeing the interactive reports
> server pages or having to use the export command manually. The PDF would
> have to be freshly generated each time, rather than simply linking to
> the PDF output from a subscription delivery.
> Is this possible?sql

Link Aspnet_User table with another .

Hi, is correct add a relation to Asp.net_User to one another table(example orders)

With column relactioned the table users with the table Orders , UserId , UserName ,

I am a little confused I need help!. Thank you

Are you seeking for PRIMARY/FOREIGN KEY between database tables?

Foreign Key Constraints:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vdbt7/html/dvovrforeignkeyconstraints.asp

Primary Key Constraints:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vdbt7/html/dvovrprimarykeyconstraints.asp

Limiting users to user sql server

Hello there
When i started using sql server i choose Windows authentication.
Now i need to move to sql server authentication so that not anyone can have
full access to Enterprice manager or the query anlyser
In fact i don't want that the administrator on the Windows 2000 server would
be the administrator on the sql server
What i need to do for this?
any help would be usefulYou can remove the administrators group from being able to log into SQL
Server. There is no changing to SQL authentication, you would change to
mixed mode which allows SQL and Windows authentication. But it sounds like
you are just wanting to restrict people in the admin group from accessing
and that is done by removing the admin groups from SQL.
HTH
Ray Higdon MCSE, MCDBA, CCNA
--
"Roy Goldhammer" <roygoldh@.hotmail.com> wrote in message
news:Og$rJBWxDHA.3224@.tk2msftngp13.phx.gbl...

quote:

---

> Hello there
> When i started using sql server i choose Windows authentication.
> Now i need to move to sql server authentication so that not anyone can

---

have

quote:

---

> full access to Enterprice manager or the query anlyser
> In fact i don't want that the administrator on the Windows 2000 server

---

would

quote:

---

> be the administrator on the sql server
> What i need to do for this?
> any help would be useful
>

---

|||Just remove the BUILTIN\Administrators login from SQL Server. But before
you do this make sure you know the sa password or have another NT account
that has sysadmin priviledge.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Limiting users to see particular databases in SSMS

Hi,
For a web hosting company, I need to grant access to users the way that when
they connect to SQL Server using SSMS, they must only be able to see their
own databases.
I tried to revoke VIEW ANY DATABASE that caused list of databases disappear
from SSMS, but how can I turn back particular database for a user?
Thanks in advance,
Leila
To limit visibility to database metadata, deny a login the VIEW ANY DATABASE
permission. After this permission is denied, a login can see only metadata
for master, tempdb, and databases that it owns.
BOL Ref:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/88ab9837-b707-43a9-8926-3e964f5a8b08.htm
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Leila" wrote:

> Hi,
> For a web hosting company, I need to grant access to users the way that when
> they connect to SQL Server using SSMS, they must only be able to see their
> own databases.
> I tried to revoke VIEW ANY DATABASE that caused list of databases disappear
> from SSMS, but how can I turn back particular database for a user?
> Thanks in advance,
> Leila
>
>
|||Hi Mohit,
The visibility of metadata is correct, but their own database does not
appear in SSMS (Object Explorer)
"Mohit K. Gupta" <mohitkgupta@.msn.com> wrote in message
news:0BE934B1-0729-462C-8D98-B3540E5BC21B@.microsoft.com...[vbcol=seagreen]
> To limit visibility to database metadata, deny a login the VIEW ANY
> DATABASE
> permission. After this permission is denied, a login can see only metadata
> for master, tempdb, and databases that it owns.
> BOL Ref:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/88ab9837-b707-43a9-8926-3e964f5a8b08.htm
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
> "Leila" wrote:
|||Leila (Leilas@.hotpop.com) writes:
> Hi Mohit,
> The visibility of metadata is correct, but their own database does not
> appear in SSMS (Object Explorer)
Do they actually own the databases, or the databases theirs by some tacit
agreement.
Try this:
CREATE LOGIN erik WITH PASSWORD='rtsoppa'
go
CREATE DATABASE eriks
ALTER AUTHORIZATION ON DATABASE::eriks TO erik
go
EXECUTE AS login = 'erik'
go
SELECT name FROM sys.databases
go
REVERT
go
DENY VIEW ANY DATABASE TO erik
go
EXECUTE AS login = 'erik'
go
SELECT name FROM sys.databases
go
REVERT
go
DROP DATABASE eriks
go
DROP LOGIN erik
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||As Erland said the user must be db_Owner or it will not work. I tested this
in SQL 2005 SP2. Thanks!
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
|||Leila
This should work if the user is the owner of the database.
Create a new SQL login "login1"
Create a user named login1 in master database
Grant CREATE DATABASE to login1
While impersonating login1, create a database called dbteste
Revoke CREATE DATABASE permission from login1
Revoke VIEW ANY DATABASE permission from PUBLIC
Register this server as login1
From the login1 session, expand database tree. Now, you should see
master, tempdb, dbteste
Grant VIEW ANY DATABASE to PUBLIC
From the login1 session, you should see all the databases
"Leila" <Leilas@.hotpop.com> wrote in message
news:uKzGwhBwHHA.4184@.TK2MSFTNGP06.phx.gbl...
> Hi,
> For a web hosting company, I need to grant access to users the way that
> when they connect to SQL Server using SSMS, they must only be able to see
> their own databases.
> I tried to revoke VIEW ANY DATABASE that caused list of databases
> disappear from SSMS, but how can I turn back particular database for a
> user?
> Thanks in advance,
> Leila
>
|||Thanks everybody!
It seems that it doesn't work for membership of the user in db_owner
database role. The login must be the owner of database, is that true?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eJ$Q76SwHHA.1524@.TK2MSFTNGP06.phx.gbl...
> Leila
> This should work if the user is the owner of the database.
> Create a new SQL login "login1"
> Create a user named login1 in master database
> Grant CREATE DATABASE to login1
> While impersonating login1, create a database called dbteste
> Revoke CREATE DATABASE permission from login1
> Revoke VIEW ANY DATABASE permission from PUBLIC
> Register this server as login1
> From the login1 session, expand database tree. Now, you should see
> master, tempdb, dbteste
> Grant VIEW ANY DATABASE to PUBLIC
> From the login1 session, you should see all the databases
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:uKzGwhBwHHA.4184@.TK2MSFTNGP06.phx.gbl...
>
|||Leila (Leilas@.hotpop.com) writes:
> It seems that it doesn't work for membership of the user in db_owner
> database role. The login must be the owner of database, is that true?
Yes, that's the way it is. To determine whether a user is entitled to
see the definition of a certain database, SQL Server looks at server-
level information only. Whether a user may be part of the db_owner role
in a certain database, would reqiure SQL Server to peek into that database,
and this could be very costly if there are many databases on the server,
and particularly if they are set to autoclose.
I have a suggestion on Connect about this:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=273830
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Limiting users to see particular databases in SSMS

Hi,
For a web hosting company, I need to grant access to users the way that when
they connect to SQL Server using SSMS, they must only be able to see their
own databases.
I tried to revoke VIEW ANY DATABASE that caused list of databases disappear
from SSMS, but how can I turn back particular database for a user?
Thanks in advance,
LeilaTo limit visibility to database metadata, deny a login the VIEW ANY DATABASE
permission. After this permission is denied, a login can see only metadata
for master, tempdb, and databases that it owns.
BOL Ref:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/88ab9837-b707-43a9-8926-3e96
4f5a8b08.htm
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Leila" wrote:

> Hi,
> For a web hosting company, I need to grant access to users the way that wh
en
> they connect to SQL Server using SSMS, they must only be able to see their
> own databases.
> I tried to revoke VIEW ANY DATABASE that caused list of databases disappea
r
> from SSMS, but how can I turn back particular database for a user?
> Thanks in advance,
> Leila
>
>|||Hi Mohit,
The visibility of metadata is correct, but their own database does not
appear in SSMS (Object Explorer)
"Mohit K. Gupta" <mohitkgupta@.msn.com> wrote in message
news:0BE934B1-0729-462C-8D98-B3540E5BC21B@.microsoft.com...[vbcol=seagreen]
> To limit visibility to database metadata, deny a login the VIEW ANY
> DATABASE
> permission. After this permission is denied, a login can see only metadata
> for master, tempdb, and databases that it owns.
> BOL Ref:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/88ab9837-b707-43a9-8926-3e
964f5a8b08.htm
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
> "Leila" wrote:
>|||Leila (Leilas@.hotpop.com) writes:
> Hi Mohit,
> The visibility of metadata is correct, but their own database does not
> appear in SSMS (Object Explorer)
Do they actually own the databases, or the databases theirs by some tacit
agreement.
Try this:
CREATE LOGIN erik WITH PASSWORD='rtsoppa'
go
CREATE DATABASE eriks
ALTER AUTHORIZATION ON DATABASE::eriks TO erik
go
EXECUTE AS login = 'erik'
go
SELECT name FROM sys.databases
go
REVERT
go
DENY VIEW ANY DATABASE TO erik
go
EXECUTE AS login = 'erik'
go
SELECT name FROM sys.databases
go
REVERT
go
DROP DATABASE eriks
go
DROP LOGIN erik
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||As Erland said the user must be db_Owner or it will not work. I tested this
in SQL 2005 SP2. Thanks!
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005|||Leila
This should work if the user is the owner of the database.
Create a new SQL login "login1"
Create a user named login1 in master database
Grant CREATE DATABASE to login1
While impersonating login1, create a database called dbteste
Revoke CREATE DATABASE permission from login1
Revoke VIEW ANY DATABASE permission from PUBLIC
Register this server as login1
From the login1 session, expand database tree. Now, you should see
master, tempdb, dbteste
Grant VIEW ANY DATABASE to PUBLIC
From the login1 session, you should see all the databases
"Leila" <Leilas@.hotpop.com> wrote in message
news:uKzGwhBwHHA.4184@.TK2MSFTNGP06.phx.gbl...
> Hi,
> For a web hosting company, I need to grant access to users the way that
> when they connect to SQL Server using SSMS, they must only be able to see
> their own databases.
> I tried to revoke VIEW ANY DATABASE that caused list of databases
> disappear from SSMS, but how can I turn back particular database for a
> user?
> Thanks in advance,
> Leila
>|||Thanks everybody!
It seems that it doesn't work for membership of the user in db_owner
database role. The login must be the owner of database, is that true?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eJ$Q76SwHHA.1524@.TK2MSFTNGP06.phx.gbl...
> Leila
> This should work if the user is the owner of the database.
> Create a new SQL login "login1"
> Create a user named login1 in master database
> Grant CREATE DATABASE to login1
> While impersonating login1, create a database called dbteste
> Revoke CREATE DATABASE permission from login1
> Revoke VIEW ANY DATABASE permission from PUBLIC
> Register this server as login1
> From the login1 session, expand database tree. Now, you should see
> master, tempdb, dbteste
> Grant VIEW ANY DATABASE to PUBLIC
> From the login1 session, you should see all the databases
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:uKzGwhBwHHA.4184@.TK2MSFTNGP06.phx.gbl...
>|||Leila (Leilas@.hotpop.com) writes:
> It seems that it doesn't work for membership of the user in db_owner
> database role. The login must be the owner of database, is that true?
Yes, that's the way it is. To determine whether a user is entitled to
see the definition of a certain database, SQL Server looks at server-
level information only. Whether a user may be part of the db_owner role
in a certain database, would reqiure SQL Server to peek into that database,
and this could be very costly if there are many databases on the server,
and particularly if they are set to autoclose.
I have a suggestion on Connect about this:
https://connect.microsoft.com/SQLSe...=2738
30
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Limiting users to see particular databases in SSMS

Hi,
For a web hosting company, I need to grant access to users the way that when
they connect to SQL Server using SSMS, they must only be able to see their
own databases.
I tried to revoke VIEW ANY DATABASE that caused list of databases disappear
from SSMS, but how can I turn back particular database for a user?
Thanks in advance,
LeilaTo limit visibility to database metadata, deny a login the VIEW ANY DATABASE
permission. After this permission is denied, a login can see only metadata
for master, tempdb, and databases that it owns.
BOL Ref:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/88ab9837-b707-43a9-8926-3e964f5a8b08.htm
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Leila" wrote:
> Hi,
> For a web hosting company, I need to grant access to users the way that when
> they connect to SQL Server using SSMS, they must only be able to see their
> own databases.
> I tried to revoke VIEW ANY DATABASE that caused list of databases disappear
> from SSMS, but how can I turn back particular database for a user?
> Thanks in advance,
> Leila
>
>|||Hi Mohit,
The visibility of metadata is correct, but their own database does not
appear in SSMS (Object Explorer)
"Mohit K. Gupta" <mohitkgupta@.msn.com> wrote in message
news:0BE934B1-0729-462C-8D98-B3540E5BC21B@.microsoft.com...
> To limit visibility to database metadata, deny a login the VIEW ANY
> DATABASE
> permission. After this permission is denied, a login can see only metadata
> for master, tempdb, and databases that it owns.
> BOL Ref:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/88ab9837-b707-43a9-8926-3e964f5a8b08.htm
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
> "Leila" wrote:
>> Hi,
>> For a web hosting company, I need to grant access to users the way that
>> when
>> they connect to SQL Server using SSMS, they must only be able to see
>> their
>> own databases.
>> I tried to revoke VIEW ANY DATABASE that caused list of databases
>> disappear
>> from SSMS, but how can I turn back particular database for a user?
>> Thanks in advance,
>> Leila
>>|||Leila (Leilas@.hotpop.com) writes:
> Hi Mohit,
> The visibility of metadata is correct, but their own database does not
> appear in SSMS (Object Explorer)
Do they actually own the databases, or the databases theirs by some tacit
agreement.
Try this:
CREATE LOGIN erik WITH PASSWORD='ärtsoppa'
go
CREATE DATABASE eriks
ALTER AUTHORIZATION ON DATABASE::eriks TO erik
go
EXECUTE AS login = 'erik'
go
SELECT name FROM sys.databases
go
REVERT
go
DENY VIEW ANY DATABASE TO erik
go
EXECUTE AS login = 'erik'
go
SELECT name FROM sys.databases
go
REVERT
go
DROP DATABASE eriks
go
DROP LOGIN erik
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||As Erland said the user must be db_Owner or it will not work. I tested this
in SQL 2005 SP2. Thanks!
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005|||Leila
This should work if the user is the owner of the database.
? Create a new SQL login "login1"
? Create a user named ?login1? in master database
? Grant CREATE DATABASE to login1
? While impersonating login1, create a database called ?dbteste?
? Revoke CREATE DATABASE permission from login1
? Revoke VIEW ANY DATABASE permission from PUBLIC
? Register this server as login1
? From the ?login1? session, expand database tree. Now, you should see
master, tempdb, dbteste
? Grant VIEW ANY DATABASE to PUBLIC
? From the ?login1? session, you should see all the databases
"Leila" <Leilas@.hotpop.com> wrote in message
news:uKzGwhBwHHA.4184@.TK2MSFTNGP06.phx.gbl...
> Hi,
> For a web hosting company, I need to grant access to users the way that
> when they connect to SQL Server using SSMS, they must only be able to see
> their own databases.
> I tried to revoke VIEW ANY DATABASE that caused list of databases
> disappear from SSMS, but how can I turn back particular database for a
> user?
> Thanks in advance,
> Leila
>|||Thanks everybody!
It seems that it doesn't work for membership of the user in db_owner
database role. The login must be the owner of database, is that true?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eJ$Q76SwHHA.1524@.TK2MSFTNGP06.phx.gbl...
> Leila
> This should work if the user is the owner of the database.
> ? Create a new SQL login "login1"
> ? Create a user named ?login1? in master database
> ? Grant CREATE DATABASE to login1
> ? While impersonating login1, create a database called ?dbteste?
> ? Revoke CREATE DATABASE permission from login1
> ? Revoke VIEW ANY DATABASE permission from PUBLIC
> ? Register this server as login1
> ? From the ?login1? session, expand database tree. Now, you should see
> master, tempdb, dbteste
> ? Grant VIEW ANY DATABASE to PUBLIC
> ? From the ?login1? session, you should see all the databases
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:uKzGwhBwHHA.4184@.TK2MSFTNGP06.phx.gbl...
>> Hi,
>> For a web hosting company, I need to grant access to users the way that
>> when they connect to SQL Server using SSMS, they must only be able to see
>> their own databases.
>> I tried to revoke VIEW ANY DATABASE that caused list of databases
>> disappear from SSMS, but how can I turn back particular database for a
>> user?
>> Thanks in advance,
>> Leila
>|||Leila (Leilas@.hotpop.com) writes:
> It seems that it doesn't work for membership of the user in db_owner
> database role. The login must be the owner of database, is that true?
Yes, that's the way it is. To determine whether a user is entitled to
see the definition of a certain database, SQL Server looks at server-
level information only. Whether a user may be part of the db_owner role
in a certain database, would reqiure SQL Server to peek into that database,
and this could be very costly if there are many databases on the server,
and particularly if they are set to autoclose.
I have a suggestion on Connect about this:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=273830
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

limiting heavy queries

Hi
I who'd like to know if there is a best accepted practice
that can guide me to write a regulation for limiting
Users and developers running Heavy queries on the server
during working hours."Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
Look up Query governer.
>|||There is a way to do this using the Query Governor configuration parameter.
You can specify a 'cost' limit for queries in where they won't run if the the
cost (based on execution plan) will exceed this value. You can't limit this
by user, but you can limit by connection using SET statement. All of this is
in Books online.
Colleen
"Oren" wrote:
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>|||The Query Governor option seems more like a stop-gap measure and won't
really solve the problem. If your users are running queries during business
hours to get information they need to do their jobs, limiting their ability
to run those queries might hurt more than it helps... If you have queries
that are taking a long time or using a lot of server resources, there are
several things you can do to improve performance - add resources to the
server, tune your indexes, optimize queries, optimize server
configuration... Also, can't tell from your statement, but if developers
are using your production servers for development and testing, you might
look at giving them their own SQL server...
Thanks,
Michael C., MCDBA
"Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>

Limiting access to certain DB's

I need to install EM and QA on my users machines, is there a way to limit their access to only certain databases in EM and QA? I only want them to see say database X in both EM and QA, and also limit what they can do it in QA(like Select, run make table/
update queries)? What would be the best way to manage this? How can I force a user to logon with a cetain Login account in EM and QA? Thanks for your help!
Easiest is to use Windows logins in SQL Server and then work with the regular security system inside SQL
Server (logins, users, roles and permissions).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"mikeb" <anonymous@.discussions.microsoft.com> wrote in message
news:F2CE354A-60B3-4914-B572-98F3DDE9D842@.microsoft.com...
> I need to install EM and QA on my users machines, is there a way to limit their access to only certain
databases in EM and QA? I only want them to see say database X in both EM and QA, and also limit what they
can do it in QA(like Select, run make table/update queries)? What would be the best way to manage this? How
can I force a user to logon with a cetain Login account in EM and QA? Thanks for your help!
|||mikeb wrote:
> I need to install EM and QA on my users machines, is there a way to
> limit their access to only certain databases in EM and QA? I only
> want them to see say database X in both EM and QA, and also limit
> what they can do it in QA(like Select, run make table/update
> queries)? What would be the best way to manage this? How can I
> force a user to logon with a cetain Login account in EM and QA?
> Thanks for your help!
What Tibor said is the best answer. In addition, you may want to have a look
at our OmniView product. It is a query tool designed for users who aren't
the DBA type. It integrates their login permissions, so data editing
controls are disabled if they don't have the appropriate Update, Insert, or
Delete permissions. If they don't have any access to particular databases,
or tables, they aren't displayed at all in the various lists.
It does not perform the schema modification functions of EM, but it is a
viable query tool to serve the purpose of QA.
Steve Troxell
Krell Software - Database Tools for MS SQL Server
http://www.krell-software.com

Limiting a users resource ie CPU, disk and/or memory

We are currently using Great Plains. This accounting package runs on SQL Server and we have performance problems running integration manager. The result is that users can not get work done when integration manager is running.
Is there any way I can limit the user running integration manager to a certain amount of CPU time and allocate the rest to the other users?
In Oracle, this is easy - I could just use resource plans, but I don't know if there is a way to do this with SQL Server 2K.
TIA
No, SQL Server does not support the ability to limit the amount of =
resources an application or a connections uses.
--=20
Keith
"ramick" <anonymous@.discussions.microsoft.com> wrote in message =
news:9327DE01-32DA-47B7-917F-E2513C31CB5C@.microsoft.com...
> We are currently using Great Plains. This accounting package runs on =
SQL Server and we have performance problems running integration manager. =
The result is that users can not get work done when integration manager =
is running.
>=20
> Is there any way I can limit the user running integration manager to a =
certain amount of CPU time and allocate the rest to the other users?
>=20
> In Oracle, this is easy - I could just use resource plans, but I don't =
know if there is a way to do this with SQL Server 2K.
>=20
> TIA

Limiting a users resource ie CPU, disk and/or memory

We are currently using Great Plains. This accounting package runs on SQL Se
rver and we have performance problems running integration manager. The resu
lt is that users can not get work done when integration manager is running.
Is there any way I can limit the user running integration manager to a certa
in amount of CPU time and allocate the rest to the other users?
In Oracle, this is easy - I could just use resource plans, but I don't know
if there is a way to do this with SQL Server 2K.
TIANo, SQL Server does not support the ability to limit the amount of =
resources an application or a connections uses.
--=20
Keith
"ramick" <anonymous@.discussions.microsoft.com> wrote in message =
news:9327DE01-32DA-47B7-917F-E2513C31CB5C@.microsoft.com...
> We are currently using Great Plains. This accounting package runs on =
SQL Server and we have performance problems running integration manager. =
The result is that users can not get work done when integration manager =
is running.
>=20
> Is there any way I can limit the user running integration manager to a =
certain amount of CPU time and allocate the rest to the other users?
>=20
> In Oracle, this is easy - I could just use resource plans, but I don't =
know if there is a way to do this with SQL Server 2K.
>=20
> TIA

Limiting a users resource ie CPU, disk and/or memory

We are currently using Great Plains. This accounting package runs on SQL Server and we have performance problems running integration manager. The result is that users can not get work done when integration manager is running
Is there any way I can limit the user running integration manager to a certain amount of CPU time and allocate the rest to the other users
In Oracle, this is easy - I could just use resource plans, but I don't know if there is a way to do this with SQL Server 2K
TIANo, SQL Server does not support the ability to limit the amount of =resources an application or a connections uses.
-- Keith
"ramick" <anonymous@.discussions.microsoft.com> wrote in message =news:9327DE01-32DA-47B7-917F-E2513C31CB5C@.microsoft.com...
> We are currently using Great Plains. This accounting package runs on =SQL Server and we have performance problems running integration manager. = The result is that users can not get work done when integration manager =is running.
> > Is there any way I can limit the user running integration manager to a =certain amount of CPU time and allocate the rest to the other users?
> > In Oracle, this is easy - I could just use resource plans, but I don't =know if there is a way to do this with SQL Server 2K.
> > TIA

Limit View in SQL 2005

When adding users to the SQL Server, is there a way to limit what DB's the
user can actually view when using Enterprise Manager?
i.e. When User1 logs into Enterprise Manger, they can only see DB1 in the
list of DB's, they can't see Master, Model, or any others?
The objective is to let a company connect to their Database, without see
what other clients/databases are hosted on the same DB server.
ThanksHi Kevin,
This is indeed possible in SQL Server 2005 but the master and tempdb
databases will be visible to all users - there is no way you can get
around that. Every user needs to have access to these databases. It's
just the way SQL Server works.
In order to explain how to make USER databases invisible to others I am
attaching the following script. It simulates a situation with three
databases, each belonging to different companies. Each company has its
own login.
create database company1_db
create database company2_db
create database company3_db
go
create login company1 with password = 'password1234*'
go
create login company2 with password = 'password1234*'
go
create login company3 with password = 'password1234*'
go
--At this point, all three logins (company1, company2 and company3)
--can see all user databases (company1_db, company2_db and company3_db).
use master
go
deny view any database to public
--At this point, all three logins (company1, company2 and company3)
--can see just the master and tempdb databases.
use company1_db
go
sp_changedbowner 'company1'
use company2_db
go
sp_changedbowner 'company2'
use company3_db
go
sp_changedbowner 'company3'
--At this point, the three logins (company1, company2 and company3)
--can see the master and tempdb databases as well as their own database.
Hope this helps!
Jonathan
Kevin A wrote:
> When adding users to the SQL Server, is there a way to limit what DB's the
> user can actually view when using Enterprise Manager?
> i.e. When User1 logs into Enterprise Manger, they can only see DB1 in the
> list of DB's, they can't see Master, Model, or any others?
> The objective is to let a company connect to their Database, without see
> what other clients/databases are hosted on the same DB server.
> Thanks
>|||JPD (jpd@.nospamplease.com) writes:
> use master
> go
> deny view any database to public
> --At this point, all three logins (company1, company2 and company3)
> --can see just the master and tempdb databases.
> use company1_db
> go
> sp_changedbowner 'company1'
>
> use company2_db
> go
> sp_changedbowner 'company2'
>
> use company3_db
> go
> sp_changedbowner 'company3'
But the apparent problem with that is there for every company are several
logins.
What SQL 2005 offers is clearly not sufficient. For this reason I submitted
this entry on Connect a while back:
https://connect.microsoft.com/SQLSe...=2738
30
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Limit the range to select on dateparameter

Hello out there,

I try to force my users to select a date not more than 6 months in the past. How can I limit the range of dateselection in the reportparameter? Any ideas?

Thank you very much!

Kind regards

dollmaker

Up

|||

I'm assuming that you have FromDate and ToDate Report parameters, which have values from a query.

Try doing this :

Set the Available values for the ToDate parameter as Non-Queried and put an expression in the LABEL and VALUES columns, evaluating the ToDate Parameter against the FromDate parameter with the DateDiff function, and then allowing only the values within 6 months.

I don't know if this is the exact scenario you're facing, but this is how I would do for my application.

Let me know how it goes. All the best!

Limit the range to select on dateparameter

Hello out there,

I try to force my users to select a date not more than 6 months in the past. How can I limit the range of dateselection in the reportparameter? Any ideas?

Thank you very much!

Kind regards

dollmaker

Up

|||

I'm assuming that you have FromDate and ToDate Report parameters, which have values from a query.

Try doing this :

Set the Available values for the ToDate parameter as Non-Queried and put an expression in the LABEL and VALUES columns, evaluating the ToDate Parameter against the FromDate parameter with the DateDiff function, and then allowing only the values within 6 months.

I don't know if this is the exact scenario you're facing, but this is how I would do for my application.

Let me know how it goes. All the best!

limit the no. of users

I have an application that uses a small SQL Server database.
What I need is to prevent the access of an amount of users to the database.
At the beginning I want to limit the access only for 2 users but I want to be able in the future to grant the access to more.u can limit no: of concurrent users at server level,but U cant limit no: of user at database level from sql server.|||Actually, I want only 2 users to be able to use my application at the same time and I cant figure out which is the best solution to implement this.|||what kind of application is that? web based or windows based?
Is that application is installed on each computer or shared thru network if it is windows based?|||It's a windows client-server application.
I am thinking of giving a session ID when a user log in. Every time the client uses the database I'll check the session ID if is valid.
When the client try to log in the 2nd time I'll give him another Session ID and I'll destroy the other one.
I have also to limit the session ID numbers to 2 for the beginning and I'll ignore users that are not in the top 2.
What do u thinck about this?|||the solution you suggested will work, but the problem with it is - it requires maintenance module to manually disconnect users those who have accidentally or by mistake closed the application/machine without proper logout.

SQL server allows you to create unique application objects and lock them during execution. I think that can be an alternative solution to the problem. check sp_getapplock on BOL. the best thing is - it automatically releases the lock as soon as the connection is lost.

Limit Report Server Access

All,

I'm looking at the possibility of allowing only certian tasks and reports to be available to users. I want the user to only have so much control...but would like them to be able to run reports, subscribe to reports and be able to use the query builder. We don't want the user to see all of the reports in the organization, just the reports for there specific department. So I don't know that I want them to see the report server itself...but maybe be able to run certian features.

Can this be done?Sure, look up the security section of the Reporting Services books online. This describes RS 2000 http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_security_v1_3hia.asp
There are some changes for Yukon, but only minor, they have to do with the introduction of Report builder.

Thanks
Tudor|||Tudor,

Thanks. I didn't mention that I am using RS 2005. But I don't know if this article adresses what I am looking for. If I can use the existing RS interface that is great. But I didn't want to show items that are not available. So for example, I will have a person log into a sales region and when they go to run reprots they will only see Sales reports. I don't want them to see executive reports in the list. I know I can limit the permissions on the reprot so they get an error, but I'm really trying to make it so they don't see what they can't run.

If not then I need to try and limit what they can do in my code. But them my question is how I can access report builder and subscription via code.

Thanks for the assistance!|||Is there a way to limit reports listed in the Report Viewer based on groups?
For example, Sales can only see Sales reports in the Report Manager. They can't see reports for other divisions, like IT, Directors, HR.|||If a certain user doesn't have READ permissions on a folder, report, datasource, they won't see it returned from the Report server SOAP APIs, not see it in report manager, SQL Management Studio, etc...

The permissions have changed slightly in RS 2005, but there are only additions to support the new features: report builder, models.

Thanks
Tudor|||Tudor,

Thanks for the answer. However, I'm not seeing the expected results.
I have 5 reports. I took away permissions on 1 report and the item still shows in the Report Manager. When I click on it, it only shows me a few properties instead of showing me the report. How can I prevent the report without adequete security from being displayed?

Thanks!|||

Local administrators on the report server machine will get read properties and read/set security on all items.
If you try to access using an account that's not in the local administrators group, you should get no access at all.

Thanks
Tudor