any way to do record login failures?

sql2000 sp3a
i'd like to keep track of login failures in a table in addition to the
sql log. is there any way to do this?
i've created an alert for error 18456, login failed for user '%ls'.
if i configure the alert to call a job, how do i get that error message
into the job so that i can insert it into a table?
also, i'd like to record the hostname or ip address of the client
machine from which the login failure occurs. i know sysprocesses has
that info once a user gets logged in, but where is that info if the
login fails?
Another option is to use a trace (or profiler) to monitor
for failed logins. You can import the trace file into a
table.
The IP and Host name won't be directly available for failed
logins. Host name isn't that reliable anyway as it's
controlled by the client. For the ip address, you would need
to capture this using a network tool.
-Sue
On Wed, 02 Jun 2004 09:04:30 -0500, ch <ch@.dontemailme.com>
wrote:

>sql2000 sp3a
>i'd like to keep track of login failures in a table in addition to the
>sql log. is there any way to do this?
>i've created an alert for error 18456, login failed for user '%ls'.
>if i configure the alert to call a job, how do i get that error message
>into the job so that i can insert it into a table?
>also, i'd like to record the hostname or ip address of the client
>machine from which the login failure occurs. i know sysprocesses has
>that info once a user gets logged in, but where is that info if the
>login fails?

any way to do record login failures?

sql2000 sp3a
i'd like to keep track of login failures in a table in addition to the
sql log. is there any way to do this?
i've created an alert for error 18456, login failed for user '%ls'.
if i configure the alert to call a job, how do i get that error message
into the job so that i can insert it into a table?
also, i'd like to record the hostname or ip address of the client
machine from which the login failure occurs. i know sysprocesses has
that info once a user gets logged in, but where is that info if the
login fails?Another option is to use a trace (or profiler) to monitor
for failed logins. You can import the trace file into a
table.
The IP and Host name won't be directly available for failed
logins. Host name isn't that reliable anyway as it's
controlled by the client. For the ip address, you would need
to capture this using a network tool.
-Sue
On Wed, 02 Jun 2004 09:04:30 -0500, ch <ch@.dontemailme.com>
wrote:

>sql2000 sp3a
>i'd like to keep track of login failures in a table in addition to the
>sql log. is there any way to do this?
>i've created an alert for error 18456, login failed for user '%ls'.
>if i configure the alert to call a job, how do i get that error message
>into the job so that i can insert it into a table?
>also, i'd like to record the hostname or ip address of the client
>machine from which the login failure occurs. i know sysprocesses has
>that info once a user gets logged in, but where is that info if the
>login fails?

any way to do record login failures?

sql2000 sp3a
i'd like to keep track of login failures in a table in addition to the
sql log. is there any way to do this?
i've created an alert for error 18456, login failed for user '%ls'.
if i configure the alert to call a job, how do i get that error message
into the job so that i can insert it into a table?
also, i'd like to record the hostname or ip address of the client
machine from which the login failure occurs. i know sysprocesses has
that info once a user gets logged in, but where is that info if the
login fails?Another option is to use a trace (or profiler) to monitor
for failed logins. You can import the trace file into a
table.
The IP and Host name won't be directly available for failed
logins. Host name isn't that reliable anyway as it's
controlled by the client. For the ip address, you would need
to capture this using a network tool.
-Sue
On Wed, 02 Jun 2004 09:04:30 -0500, ch <ch@.dontemailme.com>
wrote:
>sql2000 sp3a
>i'd like to keep track of login failures in a table in addition to the
>sql log. is there any way to do this?
>i've created an alert for error 18456, login failed for user '%ls'.
>if i configure the alert to call a job, how do i get that error message
>into the job so that i can insert it into a table?
>also, i'd like to record the hostname or ip address of the client
>machine from which the login failure occurs. i know sysprocesses has
>that info once a user gets logged in, but where is that info if the
>login fails?

Any known probs SQL2000 und Server 2003

Hello out there,
we plan to move our MSSQL2000 database to a Win 2003 server. Any reasons,
not to do so? Anything, we should be aware of?
Thank you!
Bernd
We moved dozens of servers with no problems.
"Bernd Maierhofer (dato)" <bernd.maierhofer@.dato.at> wrote in message
news:Op1fE1SHEHA.3444@.TK2MSFTNGP11.phx.gbl...
> Hello out there,
> we plan to move our MSSQL2000 database to a Win 2003 server. Any reasons,
> not to do so? Anything, we should be aware of?
> Thank you!
> Bernd
>
|||If you use distributed transactions - it needs additional configuration.
If two are not in same domain you need to disable rpc security.
I cannot remmeber links now - search MS KB.
Bojidar Alexandrov

Any known probs SQL2000 und Server 2003

Hello out there,
we plan to move our MSSQL2000 database to a Win 2003 server. Any reasons,
not to do so? Anything, we should be aware of?
Thank you!
BerndWe moved dozens of servers with no problems.
"Bernd Maierhofer (dato)" <bernd.maierhofer@.dato.at> wrote in message
news:Op1fE1SHEHA.3444@.TK2MSFTNGP11.phx.gbl...
> Hello out there,
> we plan to move our MSSQL2000 database to a Win 2003 server. Any reasons,
> not to do so? Anything, we should be aware of?
> Thank you!
> Bernd
>|||If you use distributed transactions - it needs additional configuration.
If two are not in same domain you need to disable rpc security.
I cannot remmeber links now - search MS KB.
Bojidar Alexandrov

Any known probs SQL2000 und Server 2003

Hello out there,
we plan to move our MSSQL2000 database to a Win 2003 server. Any reasons,
not to do so? Anything, we should be aware of?
Thank you!
BerndWe moved dozens of servers with no problems.
"Bernd Maierhofer (dato)" <bernd.maierhofer@.dato.at> wrote in message
news:Op1fE1SHEHA.3444@.TK2MSFTNGP11.phx.gbl...
> Hello out there,
> we plan to move our MSSQL2000 database to a Win 2003 server. Any reasons,
> not to do so? Anything, we should be aware of?
> Thank you!
> Bernd
>|||If you use distributed transactions - it needs additional configuration.
If two are not in same domain you need to disable rpc security.
I cannot remmeber links now - search MS KB.
Bojidar Alexandrov

any issues with sql2k on win2k3?

we're about to upgrade from
win2000, sql2000 sp3a standard edition, dual p3 900mhz, 2gb ram
to
win2003, sql2000 sp3a standard edition, dual xeon 3ghz hyperthreaded,
2gb ram
the only issue i could find at microsoft was the sql install issue
where win2003 wants sql sp3. any other issues to watch for?
do some people claim better performance by limiting sql server to use
only the two physical processors instead of the two physical processors
and the two logical processors?
"ch" <ch@.dontemailme.com> wrote in message
news:41A36D56.E36EF4A7@.dontemailme.com...
> we're about to upgrade from
> win2000, sql2000 sp3a standard edition, dual p3 900mhz, 2gb ram
> to
> win2003, sql2000 sp3a standard edition, dual xeon 3ghz hyperthreaded,
> 2gb ram
> the only issue i could find at microsoft was the sql install issue
> where win2003 wants sql sp3. any other issues to watch for?
I think you're covered, operating systems are comparable? In otherwords,
Windows 2000 Standard and Windows 2003 Standard?

> do some people claim better performance by limiting sql server to use
> only the two physical processors instead of the two physical processors
> and the two logical processors?
I prefer not to tinker with processor settings, rather allow the operating
system to manage the processors. in addition, Windows Server 2003 and SQL
Server 2000 does a fairly good job of dynamic memory and interfacing with
the processors. You could always run some benchmarks as there are always
certain situations, applications, etc where manual intervention may be
warranted.
Steve

any issues with sql2k on win2k3?

we're about to upgrade from
win2000, sql2000 sp3a standard edition, dual p3 900mhz, 2gb ram
to
win2003, sql2000 sp3a standard edition, dual xeon 3ghz hyperthreaded,
2gb ram
the only issue i could find at microsoft was the sql install issue
where win2003 wants sql sp3. any other issues to watch for?
do some people claim better performance by limiting sql server to use
only the two physical processors instead of the two physical processors
and the two logical processors?"ch" <ch@.dontemailme.com> wrote in message
news:41A36D56.E36EF4A7@.dontemailme.com...
> we're about to upgrade from
> win2000, sql2000 sp3a standard edition, dual p3 900mhz, 2gb ram
> to
> win2003, sql2000 sp3a standard edition, dual xeon 3ghz hyperthreaded,
> 2gb ram
> the only issue i could find at microsoft was the sql install issue
> where win2003 wants sql sp3. any other issues to watch for?
I think you're covered, operating systems are comparable? In otherwords,
Windows 2000 Standard and Windows 2003 Standard?

> do some people claim better performance by limiting sql server to use
> only the two physical processors instead of the two physical processors
> and the two logical processors?
I prefer not to tinker with processor settings, rather allow the operating
system to manage the processors. in addition, Windows Server 2003 and SQL
Server 2000 does a fairly good job of dynamic memory and interfacing with
the processors. You could always run some benchmarks as there are always
certain situations, applications, etc where manual intervention may be
warranted.
Steve

any issues with sql2k on win2k3?

we're about to upgrade from
win2000, sql2000 sp3a standard edition, dual p3 900mhz, 2gb ram
to
win2003, sql2000 sp3a standard edition, dual xeon 3ghz hyperthreaded,
2gb ram
the only issue i could find at microsoft was the sql install issue
where win2003 wants sql sp3. any other issues to watch for?
do some people claim better performance by limiting sql server to use
only the two physical processors instead of the two physical processors
and the two logical processors?"ch" <ch@.dontemailme.com> wrote in message
news:41A36D56.E36EF4A7@.dontemailme.com...
> we're about to upgrade from
> win2000, sql2000 sp3a standard edition, dual p3 900mhz, 2gb ram
> to
> win2003, sql2000 sp3a standard edition, dual xeon 3ghz hyperthreaded,
> 2gb ram
> the only issue i could find at microsoft was the sql install issue
> where win2003 wants sql sp3. any other issues to watch for?
I think you're covered, operating systems are comparable? In otherwords,
Windows 2000 Standard and Windows 2003 Standard?
> do some people claim better performance by limiting sql server to use
> only the two physical processors instead of the two physical processors
> and the two logical processors?
I prefer not to tinker with processor settings, rather allow the operating
system to manage the processors. in addition, Windows Server 2003 and SQL
Server 2000 does a fairly good job of dynamic memory and interfacing with
the processors. You could always run some benchmarks as there are always
certain situations, applications, etc where manual intervention may be
warranted.
Steve

Any increase in replication performance upgrading to server2003?

Are there any issues with sql2000 replication on
server 2003? We are adding a new distributor and
it's OS is server2003ent. Thanks,
The only thing I've come across is that DTC is disabled by default which
affects immediate updating subscribers - see this article for more info:
http://support.microsoft.com/default.aspx?kbid=817064
HTH,
Paul

Any better monitoring for locks and blocking in SQL2005?

Are the facilities for monitoring locks and blocking in SQL2005 better than
2000?
I found that in SQL2000 Enterprise Manager by the time you waited for
"current activity" to refresh, the information could have been and gone.
I'd be interested to hear if you've been using it sucessfully to do this
sort of thing.
If you want something similar to Current Activity, Activity
Monitor in Management Studio is an improvement over the
Current Activity node in Enterprise Manager. Opens in a
separate window, you have a few different view to chose
from, you can set a refresh interval.
2005 also has server level reports such as Blocking
Transactions and Top Transactions by Locks.
But just like Current Activity, you are seeing a snapshot
and you need to refresh. You have more options in 2000 to
understand the blocking, locking if you use queries to
monitor activity and it's somewhat the same in 2005.
However, there are improvements to the monitoring and
details you can get related to locking, blocking. In 2005,
you have a lot more details exposed on the waits. You can
also set up a blocked process threshold and use this with
the Blocked Process Report event class in Profiler, SQL
trace. You can also get detailed historical information
related to locking and blocking from the DMV
Sys.dm_db_index_operational_stats.
The following article has a lot of information on you can
use to monitor blocking, locking issues in 2005:
Troubleshooting Performance Problems in SQL Server 2005
http://www.microsoft.com/technet/pro.../tsprfprb.mspx
-Sue
On Thu, 19 Jan 2006 04:50:02 -0800, "James"
<James@.discussions.microsoft.com> wrote:

>Are the facilities for monitoring locks and blocking in SQL2005 better than
>2000?
>I found that in SQL2000 Enterprise Manager by the time you waited for
>"current activity" to refresh, the information could have been and gone.
>I'd be interested to hear if you've been using it sucessfully to do this
>sort of thing.
|||Night and day, across the board. SQL Server 2000 exposed very limited
information to be able to monitor. SQL Server 2005 has layer after layer
after layer of diagnostics. From DBCC commans through DMVs/DMFs, there
aren't many areas of the engine you can't get at.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"James" <James@.discussions.microsoft.com> wrote in message
news:98B66E56-8895-4040-BA63-056144C882C6@.microsoft.com...
> Are the facilities for monitoring locks and blocking in SQL2005 better
> than
> 2000?
> I found that in SQL2000 Enterprise Manager by the time you waited for
> "current activity" to refresh, the information could have been and gone.
> I'd be interested to hear if you've been using it sucessfully to do this
> sort of thing.

Any Advice on transact repl error

Hi All, We are using SQL2000 servers with transact replication to a warm
stand-by server. We are seeing the following error from the Log reader
agents.

Does anyone have any insight on this error?

The process could not execute 'sp_MSadd_repl_commands27hp'

TIA Scott B."Scott Bradley" <blah@.blah.comwrote in message
news:HTm_i.9413$ww2.2129@.newssvr19.news.prodigy.ne t...

Quote:

Originally Posted by

Hi All, We are using SQL2000 servers with transact replication to a warm
stand-by server. We are seeing the following error from the Log reader
agents.
>
Does anyone have any insight on this error?
>
The process could not execute 'sp_MSadd_repl_commands27hp'
>
TIA Scott B.
>
>

|||"Scott Bradley" <blah@.blah.comwrote in message
news:HTm_i.9413$ww2.2129@.newssvr19.news.prodigy.ne t...

Quote:

Originally Posted by

Hi All, We are using SQL2000 servers with transact replication to a warm
stand-by server. We are seeing the following error from the Log reader
agents.
>
Does anyone have any insight on this error?
>
The process could not execute 'sp_MSadd_repl_commands27hp'
>

We saw this happen from time to time. Never found the solution.

Put a retry on the job and then alert upon COMPLETION (not just failure) and
restart when needed.

Quote:

Originally Posted by

TIA Scott B.
>
>

--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||What job. I haven't been able to determine which job is calling the sp in
question.
The log reader agent retries 10 ties then 'fails'. Sometime I can get things
work by restarting teh agent. Other times I have to reboot the subscribing
server, which where I also run the distribution agents.
Thanks, Scott B.
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.comwrote in message
news:13jksd0rea3mabe@.corp.supernews.com...

Quote:

Originally Posted by

"Scott Bradley" <blah@.blah.comwrote in message
news:HTm_i.9413$ww2.2129@.newssvr19.news.prodigy.ne t...

Quote:

Originally Posted by

Hi All, We are using SQL2000 servers with transact replication to a warm
stand-by server. We are seeing the following error from the Log reader
agents.

Does anyone have any insight on this error?

The process could not execute 'sp_MSadd_repl_commands27hp'

>
We saw this happen from time to time. Never found the solution.
>
Put a retry on the job and then alert upon COMPLETION (not just failure)

and

Quote:

Originally Posted by

restart when needed.
>
>

Quote:

Originally Posted by

TIA Scott B.

>
>
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com

http://www.greenms.com/sqlserver.html

Quote:

Originally Posted by

>
>

Anti-Virus Precautions

I'm about to setup my first CRM 3.0 coupled with SQL2000 dedicated server an
d
was wondering if there are any folders or file types that the anti virus
program should be excluded from scanning to prevent corruption.
Please be specific as to each program, CRM and SQL2000.
Thank you as always for your wisdom.
He has half the deed done who has made a beginning ~ HoraceI can't say about the CRM but for SQL Server at the minimum you want to
exclude:
folders with .mdf, .ndf and .ldf files
SQL Server ad related services log files
Backup files
Here is a little more info that may be helpful.
http://support.microsoft.com/kb/309422
Andrew J. Kelly SQL MVP
"WaltB123" <WaltB123@.noemail.postalias> wrote in message
news:6FE4F82C-DD2F-43CA-96CE-32C6BC5155F0@.microsoft.com...
> I'm about to setup my first CRM 3.0 coupled with SQL2000 dedicated server
> and
> was wondering if there are any folders or file types that the anti virus
> program should be excluded from scanning to prevent corruption.
> Please be specific as to each program, CRM and SQL2000.
> Thank you as always for your wisdom.
> --
> He has half the deed done who has made a beginning ~ Horace|||Thank you for the heads up. Is there a newsgroup for CRM I can post to? I
didnt see one on the managed newsgroups list.|||Hello,
You can exclude the directories where your database files, backup files and
audit files for SQL server are stored in your antivirus program. In that way
antivirus wont scan those folders.
Thanks
Prakash
"WaltB123" wrote:

> I'm about to setup my first CRM 3.0 coupled with SQL2000 dedicated server
and
> was wondering if there are any folders or file types that the anti virus
> program should be excluded from scanning to prevent corruption.
> Please be specific as to each program, CRM and SQL2000.
> Thank you as always for your wisdom.
> --
> He has half the deed done who has made a beginning ~ Horace

ANSI_WARNINGS inconsistently in effect

I have written a VB.Net application using a SQLConnection to connect to a SQL
2000 database. The application uses an update statement in a SQLDataAdapter
to make changes to a table on the server.
The problem is that one client is getting an error with the update failing
due to string truncation. The other clients do not get an error. The only
part of the string in question that matters is the first letter, so there is
no data integrity issue.
I realize that I could put the update in a stored proc and set ANSI_WARNINGS
OFF, and then call the proc. But, I was interested in why this only is a
problem on one client.
The ANSI_WARNINGS db_option for the database is FALSE. I have searched the
MS KB and used Google Groups to search microsoft.public.* to no avail.
From what I have read, there is no way to set ANSI_WARNINGS for the
SQLConnection object. The thing that confuses me is why all clients are fine
except that one. From what I can determine, all have the same version of SQL
Server ODBC driver, etc.
Any suggestions would be appreciated.
It could be that, that particular client's table structure is different.
Check and make sure that table's column widths are the same as the ones on
the other databases.
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"A. Powers" <APowers@.discussions.microsoft.com> wrote in message
news:28CE89D3-8B4A-4218-8306-1168274499B7@.microsoft.com...
I have written a VB.Net application using a SQLConnection to connect to a
SQL
2000 database. The application uses an update statement in a SQLDataAdapter
to make changes to a table on the server.
The problem is that one client is getting an error with the update failing
due to string truncation. The other clients do not get an error. The only
part of the string in question that matters is the first letter, so there is
no data integrity issue.
I realize that I could put the update in a stored proc and set ANSI_WARNINGS
OFF, and then call the proc. But, I was interested in why this only is a
problem on one client.
The ANSI_WARNINGS db_option for the database is FALSE. I have searched the
MS KB and used Google Groups to search microsoft.public.* to no avail.
From what I have read, there is no way to set ANSI_WARNINGS for the
SQLConnection object. The thing that confuses me is why all clients are
fine
except that one. From what I can determine, all have the same version of
SQL
Server ODBC driver, etc.
Any suggestions would be appreciated.