We'd like to deploy our report servers behind our web tier in the app tier
in order to prevent our clients from being able to use url access directly.
My main concern has to do with a chance that a client may attempt to alter
the content of report parameters or otherwise probe around.
Our web code is able to forward requests to the report server and render
reports correctly, but toolbar functionality seems to be broken. The web
developer tells me that the toolbar functionality is too stateful, so
paging (as an example) won't work.
Is what we're trying to do (request forwarding) unsupported? Are my fears
regarding exposing the report server in our DMZ unwarranted? If so, I must
be missing something.What about building your own interfaace or getting the Report Stream from
Reporting Webservice to Qrite the Stream to the browser ? There you could
lock down your reporting server and connect to the RS with special lockedup
credentials.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"JoeA" <joea@.nospam.net> schrieb im Newsbeitrag
news:Xns963D69BAFC14Emailmailcom@.207.46.248.16...
> We'd like to deploy our report servers behind our web tier in the app tier
> in order to prevent our clients from being able to use url access
> directly.
> My main concern has to do with a chance that a client may attempt to alter
> the content of report parameters or otherwise probe around.
> Our web code is able to forward requests to the report server and render
> reports correctly, but toolbar functionality seems to be broken. The web
> developer tells me that the toolbar functionality is too stateful, so
> paging (as an example) won't work.
> Is what we're trying to do (request forwarding) unsupported? Are my fears
> regarding exposing the report server in our DMZ unwarranted? If so, I
> must
> be missing something.|||Thanks for the reply. We have considered that - however we didn't want to
have to recreate all of the goodies in the toolbar.
"Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
in news:#1t7uEQRFHA.2136@.TK2MSFTNGP14.phx.gbl:
> What about building your own interfaace or getting the Report Stream
> from Reporting Webservice to Qrite the Stream to the browser ? There
> you could lock down your reporting server and connect to the RS with
> special lockedup credentials.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
Showing posts with label prevent. Show all posts
Showing posts with label prevent. Show all posts
Friday, March 9, 2012
Tuesday, February 14, 2012
Deny login for SQL Server Authenticated accounts
Hi,
I want to prevent users from logging into a database temporarily (once a
weekly for a few hours), and once I've updated the tables in the database, I
need to allow all users access again.
I have looked at the system stored procedure sp_denylogin, but this only
works for NT Authenticated accounts. Is there an equivalent system stored
procedure for denying logins for accounts created with AQL Server
Authentication?
Your help will be greatly appreciated.In the script that updates this, place at the top:
ALTER DATABASE databasename SET SINGLE_USER WITH ROLLBACK IMMEDIATE
At the end of the script, put:
ALTER DATABASE databasename SET MULTI_USER
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>|||Hi,
I recommend you to start the database in SINGLE USER mode or set the
database to RESTRICTED mode before changing rhe schema.
ALTER DATABASE <DBNAME> set SINGLE_USER
or
ALTER DATABASE <DBNAME> set RESTRICTED_USER
Once the schema change is over you set back to multi user mode.
ALTER DATABASE <DBNAME> set MULTI_USER
Thanks
Hari
SQL Server MVP
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
> I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>|||Hi Hari,
Tried running this in the SQL Query Analyser, and appears to take forever.
It has now been running for over 30 minutes and still has a status of
"executing query batch"
Is this normal?
Eric
"Hari Prasad" wrote:
> Hi,
> I recommend you to start the database in SINGLE USER mode or set the
> database to RESTRICTED mode before changing rhe schema.
>
> ALTER DATABASE <DBNAME> set SINGLE_USER
> or
> ALTER DATABASE <DBNAME> set RESTRICTED_USER
>
> Once the schema change is over you set back to multi user mode.
> ALTER DATABASE <DBNAME> set MULTI_USER
>
> --
> Thanks
> Hari
> SQL Server MVP
> "Eric" <Eric@.discussions.microsoft.com> wrote in message
> news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> > Hi,
> >
> > I want to prevent users from logging into a database temporarily (once a
> > weekly for a few hours), and once I've updated the tables in the database,
> > I
> > need to allow all users access again.
> >
> > I have looked at the system stored procedure sp_denylogin, but this only
> > works for NT Authenticated accounts. Is there an equivalent system stored
> > procedure for denying logins for accounts created with AQL Server
> > Authentication?
> >
> > Your help will be greatly appreciated.
> >
> >
>
>|||It can be if someone is using the database. You can force
the connections to be killed with the termination clause in
the alter database:
ALTER DATABASE YourDatabase
SET SINGLE_USER WITH ROLLBACK IMMEDIATE
-Sue
On Mon, 25 Oct 2004 17:49:03 -0700, "Eric"
<Eric@.discussions.microsoft.com> wrote:
>Hi Hari,
>Tried running this in the SQL Query Analyser, and appears to take forever.
>It has now been running for over 30 minutes and still has a status of
>"executing query batch"
>Is this normal?
>Eric
>
>"Hari Prasad" wrote:
>> Hi,
>> I recommend you to start the database in SINGLE USER mode or set the
>> database to RESTRICTED mode before changing rhe schema.
>>
>> ALTER DATABASE <DBNAME> set SINGLE_USER
>> or
>> ALTER DATABASE <DBNAME> set RESTRICTED_USER
>>
>> Once the schema change is over you set back to multi user mode.
>> ALTER DATABASE <DBNAME> set MULTI_USER
>>
>> --
>> Thanks
>> Hari
>> SQL Server MVP
>> "Eric" <Eric@.discussions.microsoft.com> wrote in message
>> news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
>> > Hi,
>> >
>> > I want to prevent users from logging into a database temporarily (once a
>> > weekly for a few hours), and once I've updated the tables in the database,
>> > I
>> > need to allow all users access again.
>> >
>> > I have looked at the system stored procedure sp_denylogin, but this only
>> > works for NT Authenticated accounts. Is there an equivalent system stored
>> > procedure for denying logins for accounts created with AQL Server
>> > Authentication?
>> >
>> > Your help will be greatly appreciated.
>> >
>> >
>>
I want to prevent users from logging into a database temporarily (once a
weekly for a few hours), and once I've updated the tables in the database, I
need to allow all users access again.
I have looked at the system stored procedure sp_denylogin, but this only
works for NT Authenticated accounts. Is there an equivalent system stored
procedure for denying logins for accounts created with AQL Server
Authentication?
Your help will be greatly appreciated.In the script that updates this, place at the top:
ALTER DATABASE databasename SET SINGLE_USER WITH ROLLBACK IMMEDIATE
At the end of the script, put:
ALTER DATABASE databasename SET MULTI_USER
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>|||Hi,
I recommend you to start the database in SINGLE USER mode or set the
database to RESTRICTED mode before changing rhe schema.
ALTER DATABASE <DBNAME> set SINGLE_USER
or
ALTER DATABASE <DBNAME> set RESTRICTED_USER
Once the schema change is over you set back to multi user mode.
ALTER DATABASE <DBNAME> set MULTI_USER
Thanks
Hari
SQL Server MVP
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
> I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>|||Hi Hari,
Tried running this in the SQL Query Analyser, and appears to take forever.
It has now been running for over 30 minutes and still has a status of
"executing query batch"
Is this normal?
Eric
"Hari Prasad" wrote:
> Hi,
> I recommend you to start the database in SINGLE USER mode or set the
> database to RESTRICTED mode before changing rhe schema.
>
> ALTER DATABASE <DBNAME> set SINGLE_USER
> or
> ALTER DATABASE <DBNAME> set RESTRICTED_USER
>
> Once the schema change is over you set back to multi user mode.
> ALTER DATABASE <DBNAME> set MULTI_USER
>
> --
> Thanks
> Hari
> SQL Server MVP
> "Eric" <Eric@.discussions.microsoft.com> wrote in message
> news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> > Hi,
> >
> > I want to prevent users from logging into a database temporarily (once a
> > weekly for a few hours), and once I've updated the tables in the database,
> > I
> > need to allow all users access again.
> >
> > I have looked at the system stored procedure sp_denylogin, but this only
> > works for NT Authenticated accounts. Is there an equivalent system stored
> > procedure for denying logins for accounts created with AQL Server
> > Authentication?
> >
> > Your help will be greatly appreciated.
> >
> >
>
>|||It can be if someone is using the database. You can force
the connections to be killed with the termination clause in
the alter database:
ALTER DATABASE YourDatabase
SET SINGLE_USER WITH ROLLBACK IMMEDIATE
-Sue
On Mon, 25 Oct 2004 17:49:03 -0700, "Eric"
<Eric@.discussions.microsoft.com> wrote:
>Hi Hari,
>Tried running this in the SQL Query Analyser, and appears to take forever.
>It has now been running for over 30 minutes and still has a status of
>"executing query batch"
>Is this normal?
>Eric
>
>"Hari Prasad" wrote:
>> Hi,
>> I recommend you to start the database in SINGLE USER mode or set the
>> database to RESTRICTED mode before changing rhe schema.
>>
>> ALTER DATABASE <DBNAME> set SINGLE_USER
>> or
>> ALTER DATABASE <DBNAME> set RESTRICTED_USER
>>
>> Once the schema change is over you set back to multi user mode.
>> ALTER DATABASE <DBNAME> set MULTI_USER
>>
>> --
>> Thanks
>> Hari
>> SQL Server MVP
>> "Eric" <Eric@.discussions.microsoft.com> wrote in message
>> news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
>> > Hi,
>> >
>> > I want to prevent users from logging into a database temporarily (once a
>> > weekly for a few hours), and once I've updated the tables in the database,
>> > I
>> > need to allow all users access again.
>> >
>> > I have looked at the system stored procedure sp_denylogin, but this only
>> > works for NT Authenticated accounts. Is there an equivalent system stored
>> > procedure for denying logins for accounts created with AQL Server
>> > Authentication?
>> >
>> > Your help will be greatly appreciated.
>> >
>> >
>>
Deny login for SQL Server Authenticated accounts
Hi,
I want to prevent users from logging into a database temporarily (once a
weekly for a few hours), and once I've updated the tables in the database, I
need to allow all users access again.
I have looked at the system stored procedure sp_denylogin, but this only
works for NT Authenticated accounts. Is there an equivalent system stored
procedure for denying logins for accounts created with AQL Server
Authentication?
Your help will be greatly appreciated.In the script that updates this, place at the top:
ALTER DATABASE databasename SET SINGLE_USER WITH ROLLBACK IMMEDIATE
At the end of the script, put:
ALTER DATABASE databasename SET MULTI_USER
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>|||Hi,
I recommend you to start the database in SINGLE USER mode or set the
database to RESTRICTED mode before changing rhe schema.
ALTER DATABASE <DBNAME> set SINGLE_USER
or
ALTER DATABASE <DBNAME> set RESTRICTED_USER
Once the schema change is over you set back to multi user mode.
ALTER DATABASE <DBNAME> set MULTI_USER
Thanks
Hari
SQL Server MVP
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
> I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>|||Hi Hari,
Tried running this in the SQL Query Analyser, and appears to take forever.
It has now been running for over 30 minutes and still has a status of
"executing query batch"
Is this normal?
Eric
"Hari Prasad" wrote:
> Hi,
> I recommend you to start the database in SINGLE USER mode or set the
> database to RESTRICTED mode before changing rhe schema.
>
> ALTER DATABASE <DBNAME> set SINGLE_USER
> or
> ALTER DATABASE <DBNAME> set RESTRICTED_USER
>
> Once the schema change is over you set back to multi user mode.
> ALTER DATABASE <DBNAME> set MULTI_USER
>
> --
> Thanks
> Hari
> SQL Server MVP
> "Eric" <Eric@.discussions.microsoft.com> wrote in message
> news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
>
>|||It can be if someone is using the database. You can force
the connections to be killed with the termination clause in
the alter database:
ALTER DATABASE YourDatabase
SET SINGLE_USER WITH ROLLBACK IMMEDIATE
-Sue
On Mon, 25 Oct 2004 17:49:03 -0700, "Eric"
<Eric@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Hari,
>Tried running this in the SQL Query Analyser, and appears to take forever.
>It has now been running for over 30 minutes and still has a status of
>"executing query batch"
>Is this normal?
>Eric
>
>"Hari Prasad" wrote:
>
I want to prevent users from logging into a database temporarily (once a
weekly for a few hours), and once I've updated the tables in the database, I
need to allow all users access again.
I have looked at the system stored procedure sp_denylogin, but this only
works for NT Authenticated accounts. Is there an equivalent system stored
procedure for denying logins for accounts created with AQL Server
Authentication?
Your help will be greatly appreciated.In the script that updates this, place at the top:
ALTER DATABASE databasename SET SINGLE_USER WITH ROLLBACK IMMEDIATE
At the end of the script, put:
ALTER DATABASE databasename SET MULTI_USER
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>|||Hi,
I recommend you to start the database in SINGLE USER mode or set the
database to RESTRICTED mode before changing rhe schema.
ALTER DATABASE <DBNAME> set SINGLE_USER
or
ALTER DATABASE <DBNAME> set RESTRICTED_USER
Once the schema change is over you set back to multi user mode.
ALTER DATABASE <DBNAME> set MULTI_USER
Thanks
Hari
SQL Server MVP
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
> I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>|||Hi Hari,
Tried running this in the SQL Query Analyser, and appears to take forever.
It has now been running for over 30 minutes and still has a status of
"executing query batch"
Is this normal?
Eric
"Hari Prasad" wrote:
> Hi,
> I recommend you to start the database in SINGLE USER mode or set the
> database to RESTRICTED mode before changing rhe schema.
>
> ALTER DATABASE <DBNAME> set SINGLE_USER
> or
> ALTER DATABASE <DBNAME> set RESTRICTED_USER
>
> Once the schema change is over you set back to multi user mode.
> ALTER DATABASE <DBNAME> set MULTI_USER
>
> --
> Thanks
> Hari
> SQL Server MVP
> "Eric" <Eric@.discussions.microsoft.com> wrote in message
> news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
>
>|||It can be if someone is using the database. You can force
the connections to be killed with the termination clause in
the alter database:
ALTER DATABASE YourDatabase
SET SINGLE_USER WITH ROLLBACK IMMEDIATE
-Sue
On Mon, 25 Oct 2004 17:49:03 -0700, "Eric"
<Eric@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Hari,
>Tried running this in the SQL Query Analyser, and appears to take forever.
>It has now been running for over 30 minutes and still has a status of
>"executing query batch"
>Is this normal?
>Eric
>
>"Hari Prasad" wrote:
>
Deny login for SQL Server Authenticated accounts
Hi,
I want to prevent users from logging into a database temporarily (once a
weekly for a few hours), and once I've updated the tables in the database, I
need to allow all users access again.
I have looked at the system stored procedure sp_denylogin, but this only
works for NT Authenticated accounts. Is there an equivalent system stored
procedure for denying logins for accounts created with AQL Server
Authentication?
Your help will be greatly appreciated.
In the script that updates this, place at the top:
ALTER DATABASE databasename SET SINGLE_USER WITH ROLLBACK IMMEDIATE
At the end of the script, put:
ALTER DATABASE databasename SET MULTI_USER
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>
|||Hi,
I recommend you to start the database in SINGLE USER mode or set the
database to RESTRICTED mode before changing rhe schema.
ALTER DATABASE <DBNAME> set SINGLE_USER
or
ALTER DATABASE <DBNAME> set RESTRICTED_USER
Once the schema change is over you set back to multi user mode.
ALTER DATABASE <DBNAME> set MULTI_USER
Thanks
Hari
SQL Server MVP
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
> I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>
|||Hi Hari,
Tried running this in the SQL Query Analyser, and appears to take forever.
It has now been running for over 30 minutes and still has a status of
"executing query batch"
Is this normal?
Eric
"Hari Prasad" wrote:
> Hi,
> I recommend you to start the database in SINGLE USER mode or set the
> database to RESTRICTED mode before changing rhe schema.
>
> ALTER DATABASE <DBNAME> set SINGLE_USER
> or
> ALTER DATABASE <DBNAME> set RESTRICTED_USER
>
> Once the schema change is over you set back to multi user mode.
> ALTER DATABASE <DBNAME> set MULTI_USER
>
> --
> Thanks
> Hari
> SQL Server MVP
> "Eric" <Eric@.discussions.microsoft.com> wrote in message
> news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
>
>
|||It can be if someone is using the database. You can force
the connections to be killed with the termination clause in
the alter database:
ALTER DATABASE YourDatabase
SET SINGLE_USER WITH ROLLBACK IMMEDIATE
-Sue
On Mon, 25 Oct 2004 17:49:03 -0700, "Eric"
<Eric@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Hari,
>Tried running this in the SQL Query Analyser, and appears to take forever.
>It has now been running for over 30 minutes and still has a status of
>"executing query batch"
>Is this normal?
>Eric
>
>"Hari Prasad" wrote:
I want to prevent users from logging into a database temporarily (once a
weekly for a few hours), and once I've updated the tables in the database, I
need to allow all users access again.
I have looked at the system stored procedure sp_denylogin, but this only
works for NT Authenticated accounts. Is there an equivalent system stored
procedure for denying logins for accounts created with AQL Server
Authentication?
Your help will be greatly appreciated.
In the script that updates this, place at the top:
ALTER DATABASE databasename SET SINGLE_USER WITH ROLLBACK IMMEDIATE
At the end of the script, put:
ALTER DATABASE databasename SET MULTI_USER
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>
|||Hi,
I recommend you to start the database in SINGLE USER mode or set the
database to RESTRICTED mode before changing rhe schema.
ALTER DATABASE <DBNAME> set SINGLE_USER
or
ALTER DATABASE <DBNAME> set RESTRICTED_USER
Once the schema change is over you set back to multi user mode.
ALTER DATABASE <DBNAME> set MULTI_USER
Thanks
Hari
SQL Server MVP
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database temporarily (once a
> weekly for a few hours), and once I've updated the tables in the database,
> I
> need to allow all users access again.
> I have looked at the system stored procedure sp_denylogin, but this only
> works for NT Authenticated accounts. Is there an equivalent system stored
> procedure for denying logins for accounts created with AQL Server
> Authentication?
> Your help will be greatly appreciated.
>
|||Hi Hari,
Tried running this in the SQL Query Analyser, and appears to take forever.
It has now been running for over 30 minutes and still has a status of
"executing query batch"
Is this normal?
Eric
"Hari Prasad" wrote:
> Hi,
> I recommend you to start the database in SINGLE USER mode or set the
> database to RESTRICTED mode before changing rhe schema.
>
> ALTER DATABASE <DBNAME> set SINGLE_USER
> or
> ALTER DATABASE <DBNAME> set RESTRICTED_USER
>
> Once the schema change is over you set back to multi user mode.
> ALTER DATABASE <DBNAME> set MULTI_USER
>
> --
> Thanks
> Hari
> SQL Server MVP
> "Eric" <Eric@.discussions.microsoft.com> wrote in message
> news:EE89773B-5F28-4760-B1AF-8C0347A69DF9@.microsoft.com...
>
>
|||It can be if someone is using the database. You can force
the connections to be killed with the termination clause in
the alter database:
ALTER DATABASE YourDatabase
SET SINGLE_USER WITH ROLLBACK IMMEDIATE
-Sue
On Mon, 25 Oct 2004 17:49:03 -0700, "Eric"
<Eric@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Hari,
>Tried running this in the SQL Query Analyser, and appears to take forever.
>It has now been running for over 30 minutes and still has a status of
>"executing query batch"
>Is this normal?
>Eric
>
>"Hari Prasad" wrote:
Deny login for SQL Server Authenticated accounts
Hi,
I want to prevent users from logging into a database (which will occur once
a week for several hours), and once I've done the table changes, allow them
to access the db again.
How can I do this?
I've looked at sp_denylogin but appear to only work for NT Authenticated
accounts. Is there an equivalent system stored procedure for denying SQL
Server Authenticated users from logging into a db?
Thanks.
EricHi,
I recommend you to start the database in SINGLE USER mode or set the
database to RESTRICTED mode before changing rhe schema.
ALTER DATABASE <DBNAME> set SINGLE_USER
or
ALTER DATABASE <DBNAME> set RESTRICTED_USER
Once the schema change is over you set back to multi user mode.
ALTER DATABASE <DBNAME> set MULTI_USER
Thanks
Hari
SQL Server MVP
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:B43425AD-2FC0-40CB-AD96-0F160E45D1B5@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database (which will occur
> once
> a week for several hours), and once I've done the table changes, allow
> them
> to access the db again.
> How can I do this?
> I've looked at sp_denylogin but appear to only work for NT Authenticated
> accounts. Is there an equivalent system stored procedure for denying SQL
> Server Authenticated users from logging into a db?
> Thanks.
> Eric
I want to prevent users from logging into a database (which will occur once
a week for several hours), and once I've done the table changes, allow them
to access the db again.
How can I do this?
I've looked at sp_denylogin but appear to only work for NT Authenticated
accounts. Is there an equivalent system stored procedure for denying SQL
Server Authenticated users from logging into a db?
Thanks.
EricHi,
I recommend you to start the database in SINGLE USER mode or set the
database to RESTRICTED mode before changing rhe schema.
ALTER DATABASE <DBNAME> set SINGLE_USER
or
ALTER DATABASE <DBNAME> set RESTRICTED_USER
Once the schema change is over you set back to multi user mode.
ALTER DATABASE <DBNAME> set MULTI_USER
Thanks
Hari
SQL Server MVP
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:B43425AD-2FC0-40CB-AD96-0F160E45D1B5@.microsoft.com...
> Hi,
> I want to prevent users from logging into a database (which will occur
> once
> a week for several hours), and once I've done the table changes, allow
> them
> to access the db again.
> How can I do this?
> I've looked at sp_denylogin but appear to only work for NT Authenticated
> accounts. Is there an equivalent system stored procedure for denying SQL
> Server Authenticated users from logging into a db?
> Thanks.
> Eric
Subscribe to:
Posts (Atom)