More on that login problem - found the logs -

2005-11-18 12:50:12.09 logon Login failed for user 'sa'.
2005-11-18 12:50:36.85 logon Login succeeded for user 'NT
AUTHORITY\SYSTEM'. Connection: Trusted.
and some more that might be useful -
2005-11-18 12:50:40.92 logon Login succeeded for user 'NT
AUTHORITY\SYSTEM'. Connection: Trusted.
2005-11-18 12:51:01.35 logon Login succeeded for user 'NT
AUTHORITY\SYSTEM'. Connection: Trusted.
2005-11-18 12:51:53.71 logon Login failed for user 'sa'.
2005-11-18 12:57:55.45 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 12:58:01.80 logon Login failed for user 'sa'.
2005-11-18 12:58:07.73 logon Login failed for user 'a'.
2005-11-18 12:58:16.75 logon Login failed for user 'a'.
2005-11-18 12:58:23.83 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 12:58:37.46 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 12:58:37.46 spid9 Starting up database 'test'.
2005-11-18 12:58:37.46 spid9 Opening file C:\MSSQL7\DATA\test.mdf.
2005-11-18 12:58:37.49 spid9 Opening file C:\MSSQL7\DATA\test.ldf.
2005-11-18 12:58:39.34 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 12:58:42.93 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 12:59:00.99 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 13:55:32.21 logon Login succeeded for user 'ART\w tilman'.
Connection: Trusted.
2005-11-18 13:55:34.14 logon Login succeeded for user 'ART\w tilman'.
Connection: Trusted.
2005-11-18 13:55:35.05 spid10 Using 'xpsql70.dll' version '1998.11.13' to
execute extended stored procedure 'xp_msver'.
Can connect with Windows NT authentication, but not with SQL server auth. So
all my
code has stopped working ...
When I try to make a new SQL Server registration
I get server does not exist or access denied...
Hi,
Verify that you are using both SQL Server and Windows authentication using
server Properties and look in the Security tab (I believe that you are
really using both SQL Server and Windows authentication since log messages
for Windows only authentication would show "Login failed for user 'sa'.
Reason: Not associated with a trusted SQL Server connection").
Which account are you using to connect to the database? Has the password for
this account been changed?
Ben Nevarez
"Barrett Bonden" <arthur@.networks-cc.com> wrote in message
news:sIJff.13085$ha2.13022@.fe08.lga...
> 2005-11-18 12:50:12.09 logon Login failed for user 'sa'.
> 2005-11-18 12:50:36.85 logon Login succeeded for user 'NT
> AUTHORITY\SYSTEM'. Connection: Trusted.
> and some more that might be useful -
> 2005-11-18 12:50:40.92 logon Login succeeded for user 'NT
> AUTHORITY\SYSTEM'. Connection: Trusted.
> 2005-11-18 12:51:01.35 logon Login succeeded for user 'NT
> AUTHORITY\SYSTEM'. Connection: Trusted.
> 2005-11-18 12:51:53.71 logon Login failed for user 'sa'.
> 2005-11-18 12:57:55.45 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 12:58:01.80 logon Login failed for user 'sa'.
> 2005-11-18 12:58:07.73 logon Login failed for user 'a'.
> 2005-11-18 12:58:16.75 logon Login failed for user 'a'.
> 2005-11-18 12:58:23.83 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 12:58:37.46 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 12:58:37.46 spid9 Starting up database 'test'.
> 2005-11-18 12:58:37.46 spid9 Opening file C:\MSSQL7\DATA\test.mdf.
> 2005-11-18 12:58:37.49 spid9 Opening file C:\MSSQL7\DATA\test.ldf.
> 2005-11-18 12:58:39.34 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 12:58:42.93 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 12:59:00.99 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 13:55:32.21 logon Login succeeded for user 'ART\w tilman'.
> Connection: Trusted.
> 2005-11-18 13:55:34.14 logon Login succeeded for user 'ART\w tilman'.
> Connection: Trusted.
> 2005-11-18 13:55:35.05 spid10 Using 'xpsql70.dll' version '1998.11.13'
> to
> execute extended stored procedure 'xp_msver'.
>
> Can connect with Windows NT authentication, but not with SQL server auth.
> So
> all my
> code has stopped working ...
> When I try to make a new SQL Server registration
> I get server does not exist or access denied...
>
>
|||Ben:
I see that I'm using both SQL Server and Windows authentication; I see too
that under
"Startup service account" (also in the security tab) startup runs the
System Account. WHen I choose "This account" it defaults to "LocalSystem"
and a password I don't now - I'm scared to try this -
Under "registered SQL server properties" "Use windows NT authentication"
is checked. WHen I try to use SQL authenticaton nothing works - no matter
what
combo of login name and password I try ...
Should I try to make a new SQL server registration ?
All this is clear as mud - if anyone from MS reads this; boys, why do you
have
to make it so hard, so confusing , so badly documented ? It's hard enough
using it
productivly when you can get it in in the first place ...
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:#cQs$CX7FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Verify that you are using both SQL Server and Windows authentication using
> server Properties and look in the Security tab (I believe that you are
> really using both SQL Server and Windows authentication since log messages
> for Windows only authentication would show "Login failed for user 'sa'.
> Reason: Not associated with a trusted SQL Server connection").
> Which account are you using to connect to the database? Has the password
for[vbcol=seagreen]
> this account been changed?
> Ben Nevarez
>
> "Barrett Bonden" <arthur@.networks-cc.com> wrote in message
> news:sIJff.13085$ha2.13022@.fe08.lga...
auth.
>
|||If your server registration is using Windows authentication and also you can
see the server properties that means that you are a member of the system
administrators groups. Do not change the registration properties.
Also, your server is running as the system account (Security tab). Do not
change that either.
Which account is not working? sa? Is it possible that the password was
changed?
Can you create, for testing purposes, another SQL Server login and connect
with Query Analyzer using that login?
Ben Nevarez
"Barrett Bonden" <arthur@.networks-cc.com> wrote in message
news:jCQff.26341$rc7.2259@.fe12.lga...
> Ben:
> I see that I'm using both SQL Server and Windows authentication; I see
> too
> that under
> "Startup service account" (also in the security tab) startup runs the
> System Account. WHen I choose "This account" it defaults to "LocalSystem"
> and a password I don't now - I'm scared to try this -
> Under "registered SQL server properties" "Use windows NT authentication"
> is checked. WHen I try to use SQL authenticaton nothing works - no matter
> what
> combo of login name and password I try ...
> Should I try to make a new SQL server registration ?
> All this is clear as mud - if anyone from MS reads this; boys, why do you
> have
> to make it so hard, so confusing , so badly documented ? It's hard enough
> using it
> productivly when you can get it in in the first place ...
>
>
>
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:#cQs$CX7FHA.3684@.TK2MSFTNGP12.phx.gbl...
> for
> auth.
>
|||Many thanks for your help; I changed the password on the sa account, and it
now works , along, strangely , with the the other accounts I had set up.
Clearly I need to learn more about this part of the program; so far I;ve
just experimented with making it a backend for
Access -
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:OGo3LKa7FHA.1020@.TK2MSFTNGP15.phx.gbl...
> If your server registration is using Windows authentication and also you
can[vbcol=seagreen]
> see the server properties that means that you are a member of the system
> administrators groups. Do not change the registration properties.
> Also, your server is running as the system account (Security tab). Do not
> change that either.
> Which account is not working? sa? Is it possible that the password was
> changed?
> Can you create, for testing purposes, another SQL Server login and connect
> with Query Analyzer using that login?
> Ben Nevarez
>
> "Barrett Bonden" <arthur@.networks-cc.com> wrote in message
> news:jCQff.26341$rc7.2259@.fe12.lga...
"LocalSystem"[vbcol=seagreen]
matter[vbcol=seagreen]
you[vbcol=seagreen]
enough[vbcol=seagreen]
password
>
sql

More on that login problem - found the logs -

2005-11-18 12:50:12.09 logon Login failed for user 'sa'.
2005-11-18 12:50:36.85 logon Login succeeded for user 'NT
AUTHORITY\SYSTEM'. Connection: Trusted.
and some more that might be useful -
2005-11-18 12:50:40.92 logon Login succeeded for user 'NT
AUTHORITY\SYSTEM'. Connection: Trusted.
2005-11-18 12:51:01.35 logon Login succeeded for user 'NT
AUTHORITY\SYSTEM'. Connection: Trusted.
2005-11-18 12:51:53.71 logon Login failed for user 'sa'.
2005-11-18 12:57:55.45 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 12:58:01.80 logon Login failed for user 'sa'.
2005-11-18 12:58:07.73 logon Login failed for user 'a'.
2005-11-18 12:58:16.75 logon Login failed for user 'a'.
2005-11-18 12:58:23.83 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 12:58:37.46 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 12:58:37.46 spid9 Starting up database 'test'.
2005-11-18 12:58:37.46 spid9 Opening file C:\MSSQL7\DATA\test.mdf.
2005-11-18 12:58:37.49 spid9 Opening file C:\MSSQL7\DATA\test.ldf.
2005-11-18 12:58:39.34 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 12:58:42.93 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 12:59:00.99 logon Login succeeded for user 'ART\art'.
Connection: Trusted.
2005-11-18 13:55:32.21 logon Login succeeded for user 'ART\w tilman'.
Connection: Trusted.
2005-11-18 13:55:34.14 logon Login succeeded for user 'ART\w tilman'.
Connection: Trusted.
2005-11-18 13:55:35.05 spid10 Using 'xpsql70.dll' version '1998.11.13' to
execute extended stored procedure 'xp_msver'.
Can connect with Windows NT authentication, but not with SQL server auth. So
all my
code has stopped working ...
When I try to make a new SQL Server registration
I get server does not exist or access denied...Hi,
Verify that you are using both SQL Server and Windows authentication using
server Properties and look in the Security tab (I believe that you are
really using both SQL Server and Windows authentication since log messages
for Windows only authentication would show "Login failed for user 'sa'.
Reason: Not associated with a trusted SQL Server connection").
Which account are you using to connect to the database? Has the password for
this account been changed?
Ben Nevarez
"Barrett Bonden" <arthur@.networks-cc.com> wrote in message
news:sIJff.13085$ha2.13022@.fe08.lga...
> 2005-11-18 12:50:12.09 logon Login failed for user 'sa'.
> 2005-11-18 12:50:36.85 logon Login succeeded for user 'NT
> AUTHORITY\SYSTEM'. Connection: Trusted.
> and some more that might be useful -
> 2005-11-18 12:50:40.92 logon Login succeeded for user 'NT
> AUTHORITY\SYSTEM'. Connection: Trusted.
> 2005-11-18 12:51:01.35 logon Login succeeded for user 'NT
> AUTHORITY\SYSTEM'. Connection: Trusted.
> 2005-11-18 12:51:53.71 logon Login failed for user 'sa'.
> 2005-11-18 12:57:55.45 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 12:58:01.80 logon Login failed for user 'sa'.
> 2005-11-18 12:58:07.73 logon Login failed for user 'a'.
> 2005-11-18 12:58:16.75 logon Login failed for user 'a'.
> 2005-11-18 12:58:23.83 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 12:58:37.46 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 12:58:37.46 spid9 Starting up database 'test'.
> 2005-11-18 12:58:37.46 spid9 Opening file C:\MSSQL7\DATA\test.mdf.
> 2005-11-18 12:58:37.49 spid9 Opening file C:\MSSQL7\DATA\test.ldf.
> 2005-11-18 12:58:39.34 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 12:58:42.93 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 12:59:00.99 logon Login succeeded for user 'ART\art'.
> Connection: Trusted.
> 2005-11-18 13:55:32.21 logon Login succeeded for user 'ART\w tilman'.
> Connection: Trusted.
> 2005-11-18 13:55:34.14 logon Login succeeded for user 'ART\w tilman'.
> Connection: Trusted.
> 2005-11-18 13:55:35.05 spid10 Using 'xpsql70.dll' version '1998.11.13'
> to
> execute extended stored procedure 'xp_msver'.
>
> Can connect with Windows NT authentication, but not with SQL server auth.
> So
> all my
> code has stopped working ...
> When I try to make a new SQL Server registration
> I get server does not exist or access denied...
>
>|||Ben:
I see that I'm using both SQL Server and Windows authentication; I see too
that under
"Startup service account" (also in the security tab) startup runs the
System Account. WHen I choose "This account" it defaults to "LocalSystem"
and a password I don't now - I'm scared to try this -
Under "registered SQL server properties" "Use windows NT authentication"
is checked. WHen I try to use SQL authenticaton nothing works - no matter
what
combo of login name and password I try ...
Should I try to make a new SQL server registration ?
All this is clear as mud - if anyone from MS reads this; boys, why do you
have
to make it so hard, so confusing , so badly documented ? It's hard enough
using it
productivly when you can get it in in the first place ...
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:#cQs$CX7FHA.3684@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Verify that you are using both SQL Server and Windows authentication using
> server Properties and look in the Security tab (I believe that you are
> really using both SQL Server and Windows authentication since log messages
> for Windows only authentication would show "Login failed for user 'sa'.
> Reason: Not associated with a trusted SQL Server connection").
> Which account are you using to connect to the database? Has the password
for
> this account been changed?
> Ben Nevarez
>
> "Barrett Bonden" <arthur@.networks-cc.com> wrote in message
> news:sIJff.13085$ha2.13022@.fe08.lga...
auth.[vbcol=seagreen]
>|||If your server registration is using Windows authentication and also you can
see the server properties that means that you are a member of the system
administrators groups. Do not change the registration properties.
Also, your server is running as the system account (Security tab). Do not
change that either.
Which account is not working? sa? Is it possible that the password was
changed?
Can you create, for testing purposes, another SQL Server login and connect
with Query Analyzer using that login?
Ben Nevarez
"Barrett Bonden" <arthur@.networks-cc.com> wrote in message
news:jCQff.26341$rc7.2259@.fe12.lga...
> Ben:
> I see that I'm using both SQL Server and Windows authentication; I see
> too
> that under
> "Startup service account" (also in the security tab) startup runs the
> System Account. WHen I choose "This account" it defaults to "LocalSystem"
> and a password I don't now - I'm scared to try this -
> Under "registered SQL server properties" "Use windows NT authentication"
> is checked. WHen I try to use SQL authenticaton nothing works - no matter
> what
> combo of login name and password I try ...
> Should I try to make a new SQL server registration ?
> All this is clear as mud - if anyone from MS reads this; boys, why do you
> have
> to make it so hard, so confusing , so badly documented ? It's hard enough
> using it
> productivly when you can get it in in the first place ...
>
>
>
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:#cQs$CX7FHA.3684@.TK2MSFTNGP12.phx.gbl...
> for
> auth.
>|||Many thanks for your help; I changed the password on the sa account, and it
now works , along, strangely , with the the other accounts I had set up.
Clearly I need to learn more about this part of the program; so far I;ve
just experimented with making it a backend for
Access -
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:OGo3LKa7FHA.1020@.TK2MSFTNGP15.phx.gbl...
> If your server registration is using Windows authentication and also you
can
> see the server properties that means that you are a member of the system
> administrators groups. Do not change the registration properties.
> Also, your server is running as the system account (Security tab). Do not
> change that either.
> Which account is not working? sa? Is it possible that the password was
> changed?
> Can you create, for testing purposes, another SQL Server login and connect
> with Query Analyzer using that login?
> Ben Nevarez
>
> "Barrett Bonden" <arthur@.networks-cc.com> wrote in message
> news:jCQff.26341$rc7.2259@.fe12.lga...
"LocalSystem"[vbcol=seagreen]
matter[vbcol=seagreen]
you[vbcol=seagreen]
enough[vbcol=seagreen]
password[vbcol=seagreen]
>

Monitoring Production Instances.

We will soon have 200 + production instances. In an effort to be more
pro active, I am looking for a way to monitor jobs, both failed and
long running, Disk space, and other such things like CPU load etc.
I would appreicate any suggestions you might have on accomplishing
this. For instance, is there anything in reporting services that might
help accomplish this ? Most of the instances are 2k, but we also have
some 2k5.
Best Regards
SGB(sgbergkam@.gmail.com) writes:
> We will soon have 200 + production instances. In an effort to be more
> pro active, I am looking for a way to monitor jobs, both failed and
> long running, Disk space, and other such things like CPU load etc.
> I would appreicate any suggestions you might have on accomplishing
> this. For instance, is there anything in reporting services that might
> help accomplish this ? Most of the instances are 2k, but we also have
> some 2k5.

I think you should look at MOM, Microsoft Operations Manager.

--
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

Monitor show distribution agent that was removed.

While setting up transaction replication from 7 to 2000 I generate a push
subscription that failed to copy the initial schema over. I deleted the
subscription that had caused the problem and started another, that finished
okay and is replicating now. However in the Replication
Monitor-Publishers-servername-publicationname I have the failed agent from
the initial subscription and can not remove it. The same thing applies to
the Replication Monitor-Agents-Distribution Agents. It just won't go away.
SQL7 is the publisher and distributor as well as pushing a subscription to
the SQL2000 box.
Ant help would be appreciated.
Hi Charles,
From your descriptions, I understood that you would like to delete failed
agent but failed to do so. Have I understood you? If there is anything I
misunderstood, please feel free to let me know
Based on my knowledge, when you try to delete them, what's the error
message that shows you are denied to do so? More detailed information will
get us closer to the resolutions.
Secondly, I would like to strongly recommand you the following document,
which show you how to remove a replication manually
How to manually remove a replication in SQL Server 2000
http://support.microsoft.com/?id=324401
Hope this helps, if you have any questions or concerns, don't hesitate to
let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Online Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Mingqing,
I can't delete the failed subscription because it does not appear in the
list when I look in the list of subscriptions, the only place that it
appears is in the Monitor. There no way to delete it as far as I know other
than from with in the Publication Properties-Subscriptions and it does not
appear there. The current work subscription is there.
Charlie
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:uLj4km2TEHA.2436@.cpmsftngxa10.phx.gbl...
> Hi Charles,
> From your descriptions, I understood that you would like to delete failed
> agent but failed to do so. Have I understood you? If there is anything I
> misunderstood, please feel free to let me know
> Based on my knowledge, when you try to delete them, what's the error
> message that shows you are denied to do so? More detailed information will
> get us closer to the resolutions.
> Secondly, I would like to strongly recommand you the following document,
> which show you how to remove a replication manually
> How to manually remove a replication in SQL Server 2000
> http://support.microsoft.com/?id=324401
> Hope this helps, if you have any questions or concerns, don't hesitate to
> let me know. We are here to be of assistance!
> Sincerely yours,
> Mingqing Cheng
> Microsoft Online Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
|||Hi Charlie,
Thanks for your prompt updates!
Based on my knowledge, the list of Agents being displayed in Replication
Monitor are stored in the Tempdb database in the MSreplication_agent_status
table. You could removing a "left over" agent from this table will delete
it from Replication Monitor listing. You can delete any Agent from this
table without causing problems to Replication.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Mingqing,
Thanks for your reply. But it looks like it cleared it's self up over the
weekend.
Charles Deaton
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:W%2345a5fUEHA.432@.cpmsftngxa10.phx.gbl...
> Hi Charlie,
> Thanks for your prompt updates!
> Based on my knowledge, the list of Agents being displayed in Replication
> Monitor are stored in the Tempdb database in the
MSreplication_agent_status
> table. You could removing a "left over" agent from this table will delete
> it from Replication Monitor listing. You can delete any Agent from this
> table without causing problems to Replication.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>

MOM Alert when login failed for user 'sa'

I am trying to setup a MOM Alert when the SA account fails to login to SQL,
How can this be setup so SQL reports this into the windows event viewer and
not its own log?
Many thanks for any help,
AlastairIt does get logged in the application event log whenever login failure
happens for any account. (Standard install)
However, you can create a rule in MOM to capture error id:18456 with error
desc like "Login failed for user 'sa'".
--
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
"alastairn" wrote:
> I am trying to setup a MOM Alert when the SA account fails to login to SQL,
> How can this be setup so SQL reports this into the windows event viewer and
> not its own log?
> Many thanks for any help,
> Alastair
>|||Thanks for the fast response and help :)
"Saleem Hakani" wrote:
> It does get logged in the application event log whenever login failure
> happens for any account. (Standard install)
> However, you can create a rule in MOM to capture error id:18456 with error
> desc like "Login failed for user 'sa'".
> --
> Thank you,
> Saleem Hakani
> HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> Articles, SQL Clinic and a lot of SQL fun.
>
> "alastairn" wrote:
> > I am trying to setup a MOM Alert when the SA account fails to login to SQL,
> > How can this be setup so SQL reports this into the windows event viewer and
> > not its own log?
> >
> > Many thanks for any help,
> > Alastair
> >