Users in remote building (On the same VLAN? Not sure of network specifics)
can connect to the sql server in the remote building with no issues. In my
building (HQ), we were able to connect to it until this morning. Last night
the domain controller in the remote building was upgraded to Windows 2003. I
know of no other changes to this environment. I am able to use a remote
management tool (dameware) and log on locally to this sql server and then
connect. If I add a named pipes alias in my client network utility for this
server I can then connect remotely. I'm worried that the problem was caused
by the domain controller upgrade and there are several more of these
scheduled in other buildings. The one that we're having trouble with right
now is very insignificant. Should these results be repeated with subsequent
domain controller upgrades, our entire company could be affected. I can't
seem to get the right information to the domain controller folks to prove
that the cause of this issue was the upgrade nor am I really sure that this
IS the cause. The sql server is listening on port 1433 (tested using
telnet). I can ping it and access the host in every other way from here -
just can't use anything to connect to the sql server.
Thanks for your help!
Michelle
There was a kerberos service on the domain controller that was not started.
Starting this service resolved the issue. I believe that there is a KB
article on this but unfortunately, I was unable to locate it myself.
"michelle" <michelle@.nospam.com> wrote in message
news:eCqv6ohDFHA.628@.TK2MSFTNGP15.phx.gbl...
> Users in remote building (On the same VLAN? Not sure of network specifics)
> can connect to the sql server in the remote building with no issues. In my
> building (HQ), we were able to connect to it until this morning. Last
night
> the domain controller in the remote building was upgraded to Windows 2003.
I
> know of no other changes to this environment. I am able to use a remote
> management tool (dameware) and log on locally to this sql server and then
> connect. If I add a named pipes alias in my client network utility for
this
> server I can then connect remotely. I'm worried that the problem was
caused
> by the domain controller upgrade and there are several more of these
> scheduled in other buildings. The one that we're having trouble with right
> now is very insignificant. Should these results be repeated with
subsequent
> domain controller upgrades, our entire company could be affected. I can't
> seem to get the right information to the domain controller folks to prove
> that the cause of this issue was the upgrade nor am I really sure that
this
> IS the cause. The sql server is listening on port 1433 (tested using
> telnet). I can ping it and access the host in every other way from here -
> just can't use anything to connect to the sql server.
> Thanks for your help!
> Michelle
>
Showing posts with label users. Show all posts
Showing posts with label users. Show all posts
Friday, March 30, 2012
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Users in remote building (On the same VLAN? Not sure of network specifics)
can connect to the sql server in the remote building with no issues. In my
building (HQ), we were able to connect to it until this morning. Last night
the domain controller in the remote building was upgraded to Windows 2003. I
know of no other changes to this environment. I am able to use a remote
management tool (dameware) and log on locally to this sql server and then
connect. If I add a named pipes alias in my client network utility for this
server I can then connect remotely. I'm worried that the problem was caused
by the domain controller upgrade and there are several more of these
scheduled in other buildings. The one that we're having trouble with right
now is very insignificant. Should these results be repeated with subsequent
domain controller upgrades, our entire company could be affected. I can't
seem to get the right information to the domain controller folks to prove
that the cause of this issue was the upgrade nor am I really sure that this
IS the cause. The sql server is listening on port 1433 (tested using
telnet). I can ping it and access the host in every other way from here -
just can't use anything to connect to the sql server.
Thanks for your help!
MichelleThere was a kerberos service on the domain controller that was not started.
Starting this service resolved the issue. I believe that there is a KB
article on this but unfortunately, I was unable to locate it myself.
"michelle" <michelle@.nospam.com> wrote in message
news:eCqv6ohDFHA.628@.TK2MSFTNGP15.phx.gbl...
> Users in remote building (On the same VLAN? Not sure of network specifics)
> can connect to the sql server in the remote building with no issues. In my
> building (HQ), we were able to connect to it until this morning. Last
night
> the domain controller in the remote building was upgraded to Windows 2003.
I
> know of no other changes to this environment. I am able to use a remote
> management tool (dameware) and log on locally to this sql server and then
> connect. If I add a named pipes alias in my client network utility for
this
> server I can then connect remotely. I'm worried that the problem was
caused
> by the domain controller upgrade and there are several more of these
> scheduled in other buildings. The one that we're having trouble with right
> now is very insignificant. Should these results be repeated with
subsequent
> domain controller upgrades, our entire company could be affected. I can't
> seem to get the right information to the domain controller folks to prove
> that the cause of this issue was the upgrade nor am I really sure that
this
> IS the cause. The sql server is listening on port 1433 (tested using
> telnet). I can ping it and access the host in every other way from here -
> just can't use anything to connect to the sql server.
> Thanks for your help!
> Michelle
>
can connect to the sql server in the remote building with no issues. In my
building (HQ), we were able to connect to it until this morning. Last night
the domain controller in the remote building was upgraded to Windows 2003. I
know of no other changes to this environment. I am able to use a remote
management tool (dameware) and log on locally to this sql server and then
connect. If I add a named pipes alias in my client network utility for this
server I can then connect remotely. I'm worried that the problem was caused
by the domain controller upgrade and there are several more of these
scheduled in other buildings. The one that we're having trouble with right
now is very insignificant. Should these results be repeated with subsequent
domain controller upgrades, our entire company could be affected. I can't
seem to get the right information to the domain controller folks to prove
that the cause of this issue was the upgrade nor am I really sure that this
IS the cause. The sql server is listening on port 1433 (tested using
telnet). I can ping it and access the host in every other way from here -
just can't use anything to connect to the sql server.
Thanks for your help!
MichelleThere was a kerberos service on the domain controller that was not started.
Starting this service resolved the issue. I believe that there is a KB
article on this but unfortunately, I was unable to locate it myself.
"michelle" <michelle@.nospam.com> wrote in message
news:eCqv6ohDFHA.628@.TK2MSFTNGP15.phx.gbl...
> Users in remote building (On the same VLAN? Not sure of network specifics)
> can connect to the sql server in the remote building with no issues. In my
> building (HQ), we were able to connect to it until this morning. Last
night
> the domain controller in the remote building was upgraded to Windows 2003.
I
> know of no other changes to this environment. I am able to use a remote
> management tool (dameware) and log on locally to this sql server and then
> connect. If I add a named pipes alias in my client network utility for
this
> server I can then connect remotely. I'm worried that the problem was
caused
> by the domain controller upgrade and there are several more of these
> scheduled in other buildings. The one that we're having trouble with right
> now is very insignificant. Should these results be repeated with
subsequent
> domain controller upgrades, our entire company could be affected. I can't
> seem to get the right information to the domain controller folks to prove
> that the cause of this issue was the upgrade nor am I really sure that
this
> IS the cause. The sql server is listening on port 1433 (tested using
> telnet). I can ping it and access the host in every other way from here -
> just can't use anything to connect to the sql server.
> Thanks for your help!
> Michelle
>
Monday, March 26, 2012
Login failed for user '(null)'.
I'm running SQL 2000, SP3 on a W2K server and am having an issue where
users who are trying to connect to SQL Server via Windows Authenication
are getting a 'Login failed for user '(null)'. error. They have plenty
of permissions on SQL Server so that's not the issue. I've done some
testing and the only way I can get them to connect to SQL Server is if I
add them to the local admin group on the server. Has anyone else ever
seen this'
*** Sent via Developersdex http://www.developersdex.com ***Hi
Give the domain user permission to log into SQL Server.
Look at "user accounts, described" in BOL Index.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this'
>
> *** Sent via Developersdex http://www.developersdex.com ***|||Hi Rachael,
Try to rejoin to domain some of the clients.
Regards,
Daniel
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this'
>
> *** Sent via Developersdex http://www.developersdex.com ***
users who are trying to connect to SQL Server via Windows Authenication
are getting a 'Login failed for user '(null)'. error. They have plenty
of permissions on SQL Server so that's not the issue. I've done some
testing and the only way I can get them to connect to SQL Server is if I
add them to the local admin group on the server. Has anyone else ever
seen this'
*** Sent via Developersdex http://www.developersdex.com ***Hi
Give the domain user permission to log into SQL Server.
Look at "user accounts, described" in BOL Index.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this'
>
> *** Sent via Developersdex http://www.developersdex.com ***|||Hi Rachael,
Try to rejoin to domain some of the clients.
Regards,
Daniel
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this'
>
> *** Sent via Developersdex http://www.developersdex.com ***
Friday, March 23, 2012
Login failed for user (null)
Any users out there resolve this one. Thanks in advance!
Stack Trace:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details:System.Data.OleDb.OleDbException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Stack Trace:
[OleDbException (0x80004005): Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.]
System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection) +1054593
System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject) +53
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +47
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.OleDb.OleDbConnection.Open() +37
System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +121
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +137
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +83
System.Web.UI.WebControls.SqlDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +1770
System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback) +17
System.Web.UI.WebControls.DataBoundControl.PerformSelect() +149
System.Web.UI.WebControls.BaseDataBoundControl.DataBind() +70
System.Web.UI.WebControls.GridView.DataBind() +4
System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +82
System.Web.UI.WebControls.CompositeDataBoundControl.CreateChildControls() +69
System.Web.UI.Control.EnsureChildControls() +87
System.Web.UI.Control.PreRenderRecursiveInternal() +41
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1360
Did you use Windows Authentication to connect the SQL instance? The error message indicates that the SQL instance doesn't 'know' the login. You can try to add the login to the SQL instance as following:
1. Open SQL Server Management Studio
2. Go to the instance, explore 'Security'->rigth click 'Login'->'New login...', just add the account that you used to connect
Friday, March 9, 2012
Login alert
Hi all,
I want to be notified when certain users log in to SQL. I configured SQL
Mail, it works properly with several events e.g. 'Login created', but not
with "Login succeded for user '%ls' (18455). The event is set to be written
in Windows eventlog and the Audit levels is set to full. However, the alert
is not fired.
I would appreciate any idea.
Thanks,
Kolos
Kolos,
For nontrusted alerts you need to use 18454, for trusted use, 18453. The
below script works for me for alerting me to anyone logging on using
'sa' as a non-trusted connection.
IF (EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'sa login
success'))
-- Delete the alert with the same name.
EXECUTE msdb.dbo.sp_delete_alert @.name = N'sa login success'
BEGIN
EXECUTE msdb.dbo.sp_add_alert @.name = N'sa login success', @.message_id =
18454, @.severity = 0, @.enabled = 1, @.delay_between_responses = 60,
@.include_event_description_in = 4, @.event_description_keyword =
N'''sa''', @.category_name = N'[Uncategorized]'
EXECUTE msdb.dbo.sp_add_notification @.alert_name = N'sa login success',
@.operator_name = N'mark', @.notification_method = 1
END
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Kolos wrote:
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be written
> in Windows eventlog and the Audit levels is set to full. However, the alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos
|||1. Ensure the event is in the NT application log and that it comes from
sqlserver
2 Ensure that SQL Agent is running
3. Ensure that you have the proper alert setup and that is has either
notification or job set to run
4. Ensure that the operator or job is set up correctly
If the NT application log gets full, no more events can be added and
therefore alerts will not fire...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Kolos" <Kolos@.discussions.microsoft.com> wrote in message
news:41585EB8-D279-4A9D-B67E-C4F2776FA720@.microsoft.com...
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be
written
> in Windows eventlog and the Audit levels is set to full. However, the
alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos
I want to be notified when certain users log in to SQL. I configured SQL
Mail, it works properly with several events e.g. 'Login created', but not
with "Login succeded for user '%ls' (18455). The event is set to be written
in Windows eventlog and the Audit levels is set to full. However, the alert
is not fired.
I would appreciate any idea.
Thanks,
Kolos
Kolos,
For nontrusted alerts you need to use 18454, for trusted use, 18453. The
below script works for me for alerting me to anyone logging on using
'sa' as a non-trusted connection.
IF (EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'sa login
success'))
-- Delete the alert with the same name.
EXECUTE msdb.dbo.sp_delete_alert @.name = N'sa login success'
BEGIN
EXECUTE msdb.dbo.sp_add_alert @.name = N'sa login success', @.message_id =
18454, @.severity = 0, @.enabled = 1, @.delay_between_responses = 60,
@.include_event_description_in = 4, @.event_description_keyword =
N'''sa''', @.category_name = N'[Uncategorized]'
EXECUTE msdb.dbo.sp_add_notification @.alert_name = N'sa login success',
@.operator_name = N'mark', @.notification_method = 1
END
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Kolos wrote:
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be written
> in Windows eventlog and the Audit levels is set to full. However, the alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos
|||1. Ensure the event is in the NT application log and that it comes from
sqlserver
2 Ensure that SQL Agent is running
3. Ensure that you have the proper alert setup and that is has either
notification or job set to run
4. Ensure that the operator or job is set up correctly
If the NT application log gets full, no more events can be added and
therefore alerts will not fire...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Kolos" <Kolos@.discussions.microsoft.com> wrote in message
news:41585EB8-D279-4A9D-B67E-C4F2776FA720@.microsoft.com...
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be
written
> in Windows eventlog and the Audit levels is set to full. However, the
alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos
Login alert
Hi all,
I want to be notified when certain users log in to SQL. I configured SQL
Mail, it works properly with several events e.g. 'Login created', but not
with "Login succeded for user '%ls' (18455). The event is set to be written
in Windows eventlog and the Audit levels is set to full. However, the alert
is not fired.
I would appreciate any idea.
Thanks,
KolosKolos,
For nontrusted alerts you need to use 18454, for trusted use, 18453. The
below script works for me for alerting me to anyone logging on using
'sa' as a non-trusted connection.
IF (EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'sa login
success'))
-- Delete the alert with the same name.
EXECUTE msdb.dbo.sp_delete_alert @.name = N'sa login success'
BEGIN
EXECUTE msdb.dbo.sp_add_alert @.name = N'sa login success', @.message_id =18454, @.severity = 0, @.enabled = 1, @.delay_between_responses = 60,
@.include_event_description_in = 4, @.event_description_keyword =N'''sa''', @.category_name = N'[Uncategorized]'
EXECUTE msdb.dbo.sp_add_notification @.alert_name = N'sa login success',
@.operator_name = N'mark', @.notification_method = 1
END
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Kolos wrote:
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be written
> in Windows eventlog and the Audit levels is set to full. However, the alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos|||1. Ensure the event is in the NT application log and that it comes from
sqlserver
2 Ensure that SQL Agent is running
3. Ensure that you have the proper alert setup and that is has either
notification or job set to run
4. Ensure that the operator or job is set up correctly
If the NT application log gets full, no more events can be added and
therefore alerts will not fire...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Kolos" <Kolos@.discussions.microsoft.com> wrote in message
news:41585EB8-D279-4A9D-B67E-C4F2776FA720@.microsoft.com...
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be
written
> in Windows eventlog and the Audit levels is set to full. However, the
alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos
I want to be notified when certain users log in to SQL. I configured SQL
Mail, it works properly with several events e.g. 'Login created', but not
with "Login succeded for user '%ls' (18455). The event is set to be written
in Windows eventlog and the Audit levels is set to full. However, the alert
is not fired.
I would appreciate any idea.
Thanks,
KolosKolos,
For nontrusted alerts you need to use 18454, for trusted use, 18453. The
below script works for me for alerting me to anyone logging on using
'sa' as a non-trusted connection.
IF (EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'sa login
success'))
-- Delete the alert with the same name.
EXECUTE msdb.dbo.sp_delete_alert @.name = N'sa login success'
BEGIN
EXECUTE msdb.dbo.sp_add_alert @.name = N'sa login success', @.message_id =18454, @.severity = 0, @.enabled = 1, @.delay_between_responses = 60,
@.include_event_description_in = 4, @.event_description_keyword =N'''sa''', @.category_name = N'[Uncategorized]'
EXECUTE msdb.dbo.sp_add_notification @.alert_name = N'sa login success',
@.operator_name = N'mark', @.notification_method = 1
END
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Kolos wrote:
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be written
> in Windows eventlog and the Audit levels is set to full. However, the alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos|||1. Ensure the event is in the NT application log and that it comes from
sqlserver
2 Ensure that SQL Agent is running
3. Ensure that you have the proper alert setup and that is has either
notification or job set to run
4. Ensure that the operator or job is set up correctly
If the NT application log gets full, no more events can be added and
therefore alerts will not fire...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Kolos" <Kolos@.discussions.microsoft.com> wrote in message
news:41585EB8-D279-4A9D-B67E-C4F2776FA720@.microsoft.com...
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be
written
> in Windows eventlog and the Audit levels is set to full. However, the
alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos
Login alert
Hi all,
I want to be notified when certain users log in to SQL. I configured SQL
Mail, it works properly with several events e.g. 'Login created', but not
with "Login succeded for user '%ls' (18455). The event is set to be written
in Windows eventlog and the Audit levels is set to full. However, the alert
is not fired.
I would appreciate any idea.
Thanks,
KolosKolos,
For nontrusted alerts you need to use 18454, for trusted use, 18453. The
below script works for me for alerting me to anyone logging on using
'sa' as a non-trusted connection.
IF (EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'sa login
success'))
-- Delete the alert with the same name.
EXECUTE msdb.dbo.sp_delete_alert @.name = N'sa login success'
BEGIN
EXECUTE msdb.dbo.sp_add_alert @.name = N'sa login success', @.message_id =
18454, @.severity = 0, @.enabled = 1, @.delay_between_responses = 60,
@.include_event_description_in = 4, @.event_description_keyword =
N'''sa''', @.category_name = N'[Uncategorized]'
EXECUTE msdb.dbo.sp_add_notification @.alert_name = N'sa login success',
@.operator_name = N'mark', @.notification_method = 1
END
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Kolos wrote:
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be writte
n
> in Windows eventlog and the Audit levels is set to full. However, the aler
t
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos|||1. Ensure the event is in the NT application log and that it comes from
sqlserver
2 Ensure that SQL Agent is running
3. Ensure that you have the proper alert setup and that is has either
notification or job set to run
4. Ensure that the operator or job is set up correctly
If the NT application log gets full, no more events can be added and
therefore alerts will not fire...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Kolos" <Kolos@.discussions.microsoft.com> wrote in message
news:41585EB8-D279-4A9D-B67E-C4F2776FA720@.microsoft.com...
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be
written
> in Windows eventlog and the Audit levels is set to full. However, the
alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos
I want to be notified when certain users log in to SQL. I configured SQL
Mail, it works properly with several events e.g. 'Login created', but not
with "Login succeded for user '%ls' (18455). The event is set to be written
in Windows eventlog and the Audit levels is set to full. However, the alert
is not fired.
I would appreciate any idea.
Thanks,
KolosKolos,
For nontrusted alerts you need to use 18454, for trusted use, 18453. The
below script works for me for alerting me to anyone logging on using
'sa' as a non-trusted connection.
IF (EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'sa login
success'))
-- Delete the alert with the same name.
EXECUTE msdb.dbo.sp_delete_alert @.name = N'sa login success'
BEGIN
EXECUTE msdb.dbo.sp_add_alert @.name = N'sa login success', @.message_id =
18454, @.severity = 0, @.enabled = 1, @.delay_between_responses = 60,
@.include_event_description_in = 4, @.event_description_keyword =
N'''sa''', @.category_name = N'[Uncategorized]'
EXECUTE msdb.dbo.sp_add_notification @.alert_name = N'sa login success',
@.operator_name = N'mark', @.notification_method = 1
END
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Kolos wrote:
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be writte
n
> in Windows eventlog and the Audit levels is set to full. However, the aler
t
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos|||1. Ensure the event is in the NT application log and that it comes from
sqlserver
2 Ensure that SQL Agent is running
3. Ensure that you have the proper alert setup and that is has either
notification or job set to run
4. Ensure that the operator or job is set up correctly
If the NT application log gets full, no more events can be added and
therefore alerts will not fire...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Kolos" <Kolos@.discussions.microsoft.com> wrote in message
news:41585EB8-D279-4A9D-B67E-C4F2776FA720@.microsoft.com...
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be
written
> in Windows eventlog and the Audit levels is set to full. However, the
alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos
Login
I have a database that I designed for my users. Sql is the Engine and access is on the front end. I was wondering if there was a way to create a login screen, also if there was a way to create a filter that I can tie into some queries and reports. In Access you can put [] in the criteria area, type in the value and then you get that record/results. SQl server does not recognize this. What do I do, what would be the equivelant??Access has its own security login system. To enable it, give the Admin user a password. If you want to auto load a welcome screen, create a macro called Autoexec and call your welcome screen from the macro. If you want to use Access [..] facility, use linked tables and do the query in Access. This will work fine for small tables but would be slow on large amounts of data because access will need to bring all the data across the network to query it. For big tables it is better to build a SQL query in access and use a pass-through query to execute the query on the server and send just the results back to Access.
Andy
Andy
Login
following, do I work with adp, do I use the safety of the sql server to
authenticate the users, then in my front I do configure the access with my
password, for the item connection of the menu, when do I distribute that
front for each station, (do they use runtime) does the system always suggest
my name in the login, do the users complain then because every time that
they enter, t there my name, does that have solution?
ps. I didn't get to use to authenticate of the domain, I don't know because
but it didn't roll, I had to create the logins, roll, user, etc in the sql.anybody?
"Frank Dulk" <fdulk@.bol.com.br> escreveu na mensagem
news:ePLeXPUTGHA.4452@.TK2MSFTNGP12.phx.gbl...
> following, do I work with adp, do I use the safety of the sql server to
> authenticate the users, then in my front I do configure the access with my
> password, for the item connection of the menu, when do I distribute that
> front for each station, (do they use runtime) does the system always
suggest
> my name in the login, do the users complain then because every time that
> they enter, t there my name, does that have solution?
>
> ps. I didn't get to use to authenticate of the domain, I don't know
because
> but it didn't roll, I had to create the logins, roll, user, etc in the
sql.
>|||Hi Frank,
clean the connection string before distribute your front.
--
Currentproject.OpenConnection ""
--
then when you distribute reconnect it with a vba routine
bye
--
Giorgio Rancati
[Office Access MVP]
"Frank Dulk" <fdulk@.bol.com.br> ha scritto nel messaggio
news:ub02TXfTGHA.4264@.TK2MSFTNGP11.phx.gbl...
> anybody?
> "Frank Dulk" <fdulk@.bol.com.br> escreveu na mensagem
> news:ePLeXPUTGHA.4452@.TK2MSFTNGP12.phx.gbl...
my
> suggest
> because
> sql.
>
authenticate the users, then in my front I do configure the access with my
password, for the item connection of the menu, when do I distribute that
front for each station, (do they use runtime) does the system always suggest
my name in the login, do the users complain then because every time that
they enter, t there my name, does that have solution?
ps. I didn't get to use to authenticate of the domain, I don't know because
but it didn't roll, I had to create the logins, roll, user, etc in the sql.anybody?
"Frank Dulk" <fdulk@.bol.com.br> escreveu na mensagem
news:ePLeXPUTGHA.4452@.TK2MSFTNGP12.phx.gbl...
> following, do I work with adp, do I use the safety of the sql server to
> authenticate the users, then in my front I do configure the access with my
> password, for the item connection of the menu, when do I distribute that
> front for each station, (do they use runtime) does the system always
suggest
> my name in the login, do the users complain then because every time that
> they enter, t there my name, does that have solution?
>
> ps. I didn't get to use to authenticate of the domain, I don't know
because
> but it didn't roll, I had to create the logins, roll, user, etc in the
sql.
>|||Hi Frank,
clean the connection string before distribute your front.
--
Currentproject.OpenConnection ""
--
then when you distribute reconnect it with a vba routine
bye
--
Giorgio Rancati
[Office Access MVP]
"Frank Dulk" <fdulk@.bol.com.br> ha scritto nel messaggio
news:ub02TXfTGHA.4264@.TK2MSFTNGP11.phx.gbl...
> anybody?
> "Frank Dulk" <fdulk@.bol.com.br> escreveu na mensagem
> news:ePLeXPUTGHA.4452@.TK2MSFTNGP12.phx.gbl...
my
> suggest
> because
> sql.
>
Friday, February 24, 2012
Logging uses of SELECT ?
Scenario:
-I'm brand new to SQL Server 2000
-I have a vendor supplied application running on SQLServer 2k.
-I need to log which of my users has seen which data (from a
particular table). It's a healthcare privacy thing.
-The application does not do this and the vendor has no interest in
implementing it, though it seems pretty easy if one has the app code.
So I don't control the application or its code but I need to catch
who's seen what. Note that I don't have to catch it all. In other
words, I don't need to catch every instance, only whether user X has
seen patient Y's data at all. So I'm talking about a fairly small data
set. The end result I'm heading toward is a case in which a patient
demands to know who's seen his health records. I go to a db table and
say "select username from <viewlogtable> where patient_id = XXX".
How do I do that? It'd be easy if I could it were possible to write a
select trigger, or if I had some hooks into the app, but as it is I am
stumped. This is trickier than logging updates and inserts...
Thanks,
JohnThere is no such thing as a SELECT trigger. You may be able to satisfy
the requirement by analyzing the SQL log. There are some third party
products that can be of use. Do a google on "Lumigent" for literature
on their product.
HTH
=======================================
Everyone here speaks SQL; some are more fluent, others less. When
describing your SQL object (table, etc.), do so in the language that we
all understand - SQL, not English. It makes it easier to understand
your issue and makes it more likely that you will get the assistance
that you are asking for.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||"John" <jgoodlea@.fhcrc.org> wrote in message
news:80ff7fc9.0312151444.41c57adc@.posting.google.c om...
> Scenario:
> -I'm brand new to SQL Server 2000
> -I have a vendor supplied application running on SQLServer 2k.
> -I need to log which of my users has seen which data (from a
> particular table). It's a healthcare privacy thing.
> -The application does not do this and the vendor has no interest in
> implementing it, though it seems pretty easy if one has the app code.
> So I don't control the application or its code but I need to catch
> who's seen what. Note that I don't have to catch it all. In other
> words, I don't need to catch every instance, only whether user X has
> seen patient Y's data at all. So I'm talking about a fairly small data
> set. The end result I'm heading toward is a case in which a patient
> demands to know who's seen his health records. I go to a db table and
> say "select username from <viewlogtable> where patient_id = XXX".
Unfortunately I can't see any way of doing that. There's no such thing as a
select trigger.
As another poster said, Lumigent may do this, but I doubt it since I don't
believe Selects are logged at all. (wouldn't make much sense.)
Another option is to run the SQL Profiler and setup a profile to look for
JUST selects, etc. This solution actually might work fairly well
short-term. And even long-term if you really tighten the profile down to
record ONLY what you need.
> How do I do that? It'd be easy if I could it were possible to write a
> select trigger, or if I had some hooks into the app, but as it is I am
> stumped. This is trickier than logging updates and inserts...
Really what the vendor should be doing is all access through stored procs.
Then the stored proc could handle security and handle logging.
> Thanks,
> John|||You would have to ensure that the users had to view that data by executing a
stored procedure, not with a direct SELECT statement.
I'm not sure how much control you have over the application, or if you can
modify it, but this is certainly a way of 'logging' SELECT statements
made against a table or set of tables. If you can, in fact, edit the
application then you can edit it to execute a procedure that simply inserts
into the log and selects as this <simplified>:
DECLARE PROCEDURE ViewPatientRecords
(
@.PatientID int
,@.UserID int
)
AS
INSERT INTO ViewLogTable(Patient_ID, Viewer_ID, View_Date)
VALUES(@.Patient, @.UserID, GETDATE())
SELECT *
FROM Patient_Record
WHERE Patient_ID = @.PatientID
"John" <jgoodlea@.fhcrc.org> wrote in message
news:80ff7fc9.0312151444.41c57adc@.posting.google.c om...
> Scenario:
> -I'm brand new to SQL Server 2000
> -I have a vendor supplied application running on SQLServer 2k.
> -I need to log which of my users has seen which data (from a
> particular table). It's a healthcare privacy thing.
> -The application does not do this and the vendor has no interest in
> implementing it, though it seems pretty easy if one has the app code.
> So I don't control the application or its code but I need to catch
> who's seen what. Note that I don't have to catch it all. In other
> words, I don't need to catch every instance, only whether user X has
> seen patient Y's data at all. So I'm talking about a fairly small data
> set. The end result I'm heading toward is a case in which a patient
> demands to know who's seen his health records. I go to a db table and
> say "select username from <viewlogtable> where patient_id = XXX".
> How do I do that? It'd be easy if I could it were possible to write a
> select trigger, or if I had some hooks into the app, but as it is I am
> stumped. This is trickier than logging updates and inserts...
> Thanks,
> John
Logging User Activity
I would like to log which users are running what queries on our SQL Server 2005. Is there a way to do this?
I have both domain users and SQL users using the server. In the Windows logs I can see when a domain user logs in, however, the SQL users are logged in as anonymous. Even so, I can't tell what the users are doing on the system.
I have several websites and other tools that use SQL logins. We did this so users wouldn't need to know a password. I would like to know which of those tools are being used. Since most tools use a specfic set of views, if I could measure the use of the users and those views, I would know which ones can be decommissioned.
If I should post this in another forum, please let me know. This seemed like the best place.
Rob
That is a task for SQL Profiler. If you are using Edition other than Express, you will have the Profiler tool. It should have been installed with SSMS and the other client tools.
Verify your Edition and we can give you more directed help.
|||as Arnie said either you can use built in tool Profiler or you can use system SP to trace the system activities
Refer :
http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm
Madhu
|||
Arnie Rowland wrote:
That is a task for SQL Profiler. If you are using Edition other than Express, you will have the Profiler tool. It should have been installed with SSMS and the other client tools.
Verify your Edition and we can give you more directed help.
Enterprise edition, I believe. However, I've tried to verify and I'm not sure how to do that. I do know it is not the Express edition. I did find the SQL Profiler program.
Rob
|||You can verify your Edition, Service Pack, etc. using:
SELECT @.@.VERSION
(or)
SELECT
SERVERPROPERTY( Edition ),
SERVERPROPERTY( ProductLevel )
Here are some resouces that will guide you with using SQL Profiler.
Profiler -How To: Use SQL Profiler
http://msdn2.microsoft.com/en-us/library/ms979207.aspx
Profiler -Introduction
http://www.developer.com/db/article.php/3482216
Profiler -SQL Profiler Tips and Tricks
http://www.developer.com/tech/article.php/3490086
Profiler - Step-By-Step: An introduction to SQL Server Profiler
http://articles.techrepublic.com.com/5100-6329_11-5054787.html
Profiler -Tracing SQL Statements
http://sqljunkies.com/Article/9513605D-FF3B-45AE-8056-ADF30772C1A9.scuk
Profiler -Use SQL Profiler to diagnose SQL Server performance issues
http://articles.techrepublic.com.com/5100-1035_11-1043670.html
Profiler -Using Profiler to Identify Poorly Performing Queries
http://www.sql-server-performance.com/sql_server_performance_audit10.asp
Profiler -Using SQL Profiler
2000 http://www.microsoft.com/technet/prodtechnol/sql/70/tips/sqlprof.mspx
2005 http://msdn2.microsoft.com/en-us/library/ms181091.aspx
Arnie - thank you. I did some initial setup but can see I need to trim down the events being logged.
Rob
Logging User
Hi,
I am trying to log the exact user (a.k.a., Domain/User) into a column in X
data table. Currently, our users login with a connection string passing
Mixed Mode Authentication with username/pwd. Again, what we want to capture
domain/user login info - "SUSER_SNAME" captures the connection string info.
Thanks!Chris,
TMK this would require your end-users to log into SQL Server using Windows
Authenticated accounts which is a best practice. This approach is more
secure and allows for better auditing.
HTH
Jerry
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:OXlICL3fGHA.3456@.TK2MSFTNGP05.phx.gbl...
> Hi,
> I am trying to log the exact user (a.k.a., Domain/User) into a column in X
> data table. Currently, our users login with a connection string passing
> Mixed Mode Authentication with username/pwd. Again, what we want to
> capture domain/user login info - "SUSER_SNAME" captures the connection
> string info.
> Thanks!
>|||Thank you - now I have to figure out why are are then using Mixed Mode
authentication I guess.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%236D8ja3fGHA.2032@.TK2MSFTNGP02.phx.gbl...
> Chris,
> TMK this would require your end-users to log into SQL Server using Windows
> Authenticated accounts which is a best practice. This approach is more
> secure and allows for better auditing.
> HTH
> Jerry
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:OXlICL3fGHA.3456@.TK2MSFTNGP05.phx.gbl...
>> Hi,
>> I am trying to log the exact user (a.k.a., Domain/User) into a column in
>> X data table. Currently, our users login with a connection string
>> passing Mixed Mode Authentication with username/pwd. Again, what we want
>> to capture domain/user login info - "SUSER_SNAME" captures the connection
>> string info.
>> Thanks!
>
I am trying to log the exact user (a.k.a., Domain/User) into a column in X
data table. Currently, our users login with a connection string passing
Mixed Mode Authentication with username/pwd. Again, what we want to capture
domain/user login info - "SUSER_SNAME" captures the connection string info.
Thanks!Chris,
TMK this would require your end-users to log into SQL Server using Windows
Authenticated accounts which is a best practice. This approach is more
secure and allows for better auditing.
HTH
Jerry
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:OXlICL3fGHA.3456@.TK2MSFTNGP05.phx.gbl...
> Hi,
> I am trying to log the exact user (a.k.a., Domain/User) into a column in X
> data table. Currently, our users login with a connection string passing
> Mixed Mode Authentication with username/pwd. Again, what we want to
> capture domain/user login info - "SUSER_SNAME" captures the connection
> string info.
> Thanks!
>|||Thank you - now I have to figure out why are are then using Mixed Mode
authentication I guess.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%236D8ja3fGHA.2032@.TK2MSFTNGP02.phx.gbl...
> Chris,
> TMK this would require your end-users to log into SQL Server using Windows
> Authenticated accounts which is a best practice. This approach is more
> secure and allows for better auditing.
> HTH
> Jerry
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:OXlICL3fGHA.3456@.TK2MSFTNGP05.phx.gbl...
>> Hi,
>> I am trying to log the exact user (a.k.a., Domain/User) into a column in
>> X data table. Currently, our users login with a connection string
>> passing Mixed Mode Authentication with username/pwd. Again, what we want
>> to capture domain/user login info - "SUSER_SNAME" captures the connection
>> string info.
>> Thanks!
>
Logging User
Hi,
I am trying to log the exact user (a.k.a., Domain/User) into a column in X
data table. Currently, our users login with a connection string passing
Mixed Mode Authentication with username/pwd. Again, what we want to capture
domain/user login info - "SUSER_SNAME" captures the connection string info.
Thanks!Chris,
TMK this would require your end-users to log into SQL Server using Windows
Authenticated accounts which is a best practice. This approach is more
secure and allows for better auditing.
HTH
Jerry
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:OXlICL3fGHA.3456@.TK2MSFTNGP05.phx.gbl...
> Hi,
> I am trying to log the exact user (a.k.a., Domain/User) into a column in X
> data table. Currently, our users login with a connection string passing
> Mixed Mode Authentication with username/pwd. Again, what we want to
> capture domain/user login info - "SUSER_SNAME" captures the connection
> string info.
> Thanks!
>|||Thank you - now I have to figure out why are are then using Mixed Mode
authentication I guess.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%236D8ja3fGHA.2032@.TK2MSFTNGP02.phx.gbl...
> Chris,
> TMK this would require your end-users to log into SQL Server using Windows
> Authenticated accounts which is a best practice. This approach is more
> secure and allows for better auditing.
> HTH
> Jerry
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:OXlICL3fGHA.3456@.TK2MSFTNGP05.phx.gbl...
>
I am trying to log the exact user (a.k.a., Domain/User) into a column in X
data table. Currently, our users login with a connection string passing
Mixed Mode Authentication with username/pwd. Again, what we want to capture
domain/user login info - "SUSER_SNAME" captures the connection string info.
Thanks!Chris,
TMK this would require your end-users to log into SQL Server using Windows
Authenticated accounts which is a best practice. This approach is more
secure and allows for better auditing.
HTH
Jerry
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:OXlICL3fGHA.3456@.TK2MSFTNGP05.phx.gbl...
> Hi,
> I am trying to log the exact user (a.k.a., Domain/User) into a column in X
> data table. Currently, our users login with a connection string passing
> Mixed Mode Authentication with username/pwd. Again, what we want to
> capture domain/user login info - "SUSER_SNAME" captures the connection
> string info.
> Thanks!
>|||Thank you - now I have to figure out why are are then using Mixed Mode
authentication I guess.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%236D8ja3fGHA.2032@.TK2MSFTNGP02.phx.gbl...
> Chris,
> TMK this would require your end-users to log into SQL Server using Windows
> Authenticated accounts which is a best practice. This approach is more
> secure and allows for better auditing.
> HTH
> Jerry
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:OXlICL3fGHA.3456@.TK2MSFTNGP05.phx.gbl...
>
Monday, February 20, 2012
Logging Off Users
I am trying to setup a DB Maintanance Plan and am getting an Error 5070:
Database state cannot be changed while other users are using the database.
Does anyone know what microsoft sql command would be to log off all the
users. (Like Oralce command of shutdown immediate.)
Thanks.Joel,
If its SQL Server 2000, you can use:
ALTER DATABASE <databasename >
SET single_user WITH ROLLBACK IMMEDIATE
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Joel" <nowhere@.nowhere.com> wrote in message
news:%23BLYt86SDHA.2144@.TK2MSFTNGP11.phx.gbl...
> I am trying to setup a DB Maintanance Plan and am getting an Error 5070:
> Database state cannot be changed while other users are using the database.
> Does anyone know what microsoft sql command would be to log off all the
> users. (Like Oralce command of shutdown immediate.)
> Thanks.
>|||Thanks
"Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:OCNoaE7SDHA.2004@.TK2MSFTNGP11.phx.gbl...
> Joel,
> If its SQL Server 2000, you can use:
> ALTER DATABASE <databasename >
> SET single_user WITH ROLLBACK IMMEDIATE
> --
> Dinesh.
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Joel" <nowhere@.nowhere.com> wrote in message
> news:%23BLYt86SDHA.2144@.TK2MSFTNGP11.phx.gbl...
> > I am trying to setup a DB Maintanance Plan and am getting an Error 5070:
> > Database state cannot be changed while other users are using the
database.
> >
> > Does anyone know what microsoft sql command would be to log off all the
> > users. (Like Oralce command of shutdown immediate.)
> >
> > Thanks.
> >
> >
>
Database state cannot be changed while other users are using the database.
Does anyone know what microsoft sql command would be to log off all the
users. (Like Oralce command of shutdown immediate.)
Thanks.Joel,
If its SQL Server 2000, you can use:
ALTER DATABASE <databasename >
SET single_user WITH ROLLBACK IMMEDIATE
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Joel" <nowhere@.nowhere.com> wrote in message
news:%23BLYt86SDHA.2144@.TK2MSFTNGP11.phx.gbl...
> I am trying to setup a DB Maintanance Plan and am getting an Error 5070:
> Database state cannot be changed while other users are using the database.
> Does anyone know what microsoft sql command would be to log off all the
> users. (Like Oralce command of shutdown immediate.)
> Thanks.
>|||Thanks
"Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:OCNoaE7SDHA.2004@.TK2MSFTNGP11.phx.gbl...
> Joel,
> If its SQL Server 2000, you can use:
> ALTER DATABASE <databasename >
> SET single_user WITH ROLLBACK IMMEDIATE
> --
> Dinesh.
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Joel" <nowhere@.nowhere.com> wrote in message
> news:%23BLYt86SDHA.2144@.TK2MSFTNGP11.phx.gbl...
> > I am trying to setup a DB Maintanance Plan and am getting an Error 5070:
> > Database state cannot be changed while other users are using the
database.
> >
> > Does anyone know what microsoft sql command would be to log off all the
> > users. (Like Oralce command of shutdown immediate.)
> >
> > Thanks.
> >
> >
>
Subscribe to:
Posts (Atom)