Any way to run a invisible trace on Security Audit?

Is there anyway I could run an Audit trace on SQl Server which records SQL Server System Admin Login/Logout , failed login and machine names I don't want the trace window to show on screen however would like a file generated for later viewing. Also due to Firewall issues we have, We don't have SQL tools enabled to connect to that server.Yes, you can configure SQL 2000 Auditing (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_2ard.asp), up through the C2 level. Unfortunately there isn't a "cookbook" approach for doing it, you really need to understand what you are doing, and the consequences and benefits of each decision.

-PatP|||I found out . Thanks for reply. C2 auditing however is not needed . I found out that from SQL Profiler , you can script the whole trace as SQL and execute it in ISQLW . This gives back a Trace ID . Next you have to run sp_trace_Setstatus @.traceID, 1 to run it .

Thanks for responding . I appreciate that

Any way to repair the damage backup file?

Maybe post to wrong group, I am sorry.
If my backup file has error so that the restore is failed, is there any way
to repair the damage backup file?
(The restore procedure of 2005 report there is an error on page 65535:-1)
Thx.
To the best of my knowledge, there's no repair option for a backup. But in 2005, you have the
CONTINUE_AFTER_ERROR option for the RESTORE command. Of could, you will then have a database win
some corruption which you need to handle.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Frank Lee" <Reply@.to.newsgroup> wrote in message news:%23VMMehtDGHA.644@.TK2MSFTNGP09.phx.gbl...
> Maybe post to wrong group, I am sorry.
> If my backup file has error so that the restore is failed, is there any way to repair the damage
> backup file?
> (The restore procedure of 2005 report there is an error on page 65535:-1)
> Thx.
>
|||I see. Thanks. Good news for me.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
??:eWH4mgwDGHA.2924@.tk2msftngp13.phx.gbl...
> To the best of my knowledge, there's no repair option for a backup. But in
> 2005, you have the CONTINUE_AFTER_ERROR option for the RESTORE command. Of
> could, you will then have a database win some corruption which you need to
> handle.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Frank Lee" <Reply@.to.newsgroup> wrote in message
> news:%23VMMehtDGHA.644@.TK2MSFTNGP09.phx.gbl...
>

Any way to repair the damage backup file?

Maybe post to wrong group, I am sorry.
If my backup file has error so that the restore is failed, is there any way
to repair the damage backup file?
(The restore procedure of 2005 report there is an error on page 65535:-1)
Thx.To the best of my knowledge, there's no repair option for a backup. But in 2005, you have the
CONTINUE_AFTER_ERROR option for the RESTORE command. Of could, you will then have a database win
some corruption which you need to handle.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Frank Lee" <Reply@.to.newsgroup> wrote in message news:%23VMMehtDGHA.644@.TK2MSFTNGP09.phx.gbl...
> Maybe post to wrong group, I am sorry.
> If my backup file has error so that the restore is failed, is there any way to repair the damage
> backup file?
> (The restore procedure of 2005 report there is an error on page 65535:-1)
> Thx.
>|||I see. Thanks. Good news for me.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
'?:eWH4mgwDGHA.2924@.tk2msftngp13.phx.gbl...
> To the best of my knowledge, there's no repair option for a backup. But in
> 2005, you have the CONTINUE_AFTER_ERROR option for the RESTORE command. Of
> could, you will then have a database win some corruption which you need to
> handle.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Frank Lee" <Reply@.to.newsgroup> wrote in message
> news:%23VMMehtDGHA.644@.TK2MSFTNGP09.phx.gbl...
>> Maybe post to wrong group, I am sorry.
>> If my backup file has error so that the restore is failed, is there any
>> way to repair the damage backup file?
>> (The restore procedure of 2005 report there is an error on page 65535:-1)
>> Thx.
>

Any way to repair the damage backup file?

Maybe post to wrong group, I am sorry.
If my backup file has error so that the restore is failed, is there any way
to repair the damage backup file?
(The restore procedure of 2005 report there is an error on page 65535:-1)
Thx.To the best of my knowledge, there's no repair option for a backup. But in 2
005, you have the
CONTINUE_AFTER_ERROR option for the RESTORE command. Of could, you will then
have a database win
some corruption which you need to handle.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Frank Lee" <Reply@.to.newsgroup> wrote in message news:%23VMMehtDGHA.644@.TK2MSFTNGP09.phx.gb
l...
> Maybe post to wrong group, I am sorry.
> If my backup file has error so that the restore is failed, is there any wa
y to repair the damage
> backup file?
> (The restore procedure of 2005 report there is an error on page 65535:-1)
> Thx.
>|||I see. Thanks. Good news for me.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
'?:eWH4mgwDGHA.2924@.tk2msftngp13.phx.gbl...
> To the best of my knowledge, there's no repair option for a backup. But in
> 2005, you have the CONTINUE_AFTER_ERROR option for the RESTORE command. Of
> could, you will then have a database win some corruption which you need to
> handle.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Frank Lee" <Reply@.to.newsgroup> wrote in message
> news:%23VMMehtDGHA.644@.TK2MSFTNGP09.phx.gbl...
>sql

Any way to disable SQL logins after failed tries?

We're using a canned app that only uses SQL Server logins (it will NOT use Windows logins to access SQL Server)

SQL Server logins seem to lack even the most rudimentary security features such as expiring passwords and automatic disabling after a set number of failed logins. Bad. Bad Microsoft.

Has anyone figured out a way to graft this on after-the-fact?

I can do it in an awkward fashion by auditing failed logins and going back to read the error log, but this isn't real time by any stretch.To the best of my knowledge, there is no innate feature in MS SQL that will allow you manage SQL Server logins as you wish. This lack has been noted before (cross your fingers, MS will deal with this in Yukon).

We wrote a custom app and created this kind of failed-login checking, but that does not sound like an option for you.

Can you do something with a scheduled job at the SQL error log (you'd have to enable logging of failed login attempts)?

I think there is a way to load the error log as a table. Then you could search for failed logins and (if the number exceeded your threshold) disable it.

I think it's doable, but I have not had the need to accomplish this particular task.

Regards,

hmscott|||Originally posted by hmscott
To the best of my knowledge, there is no innate feature in MS SQL that will allow you manage SQL Server logins as you wish. This lack has been noted before (cross your fingers, MS will deal with this in Yukon).

We wrote a custom app and created this kind of failed-login checking, but that does not sound like an option for you.

Can you do something with a scheduled job at the SQL error log (you'd have to enable logging of failed login attempts)?

I think there is a way to load the error log as a table. Then you could search for failed logins and (if the number exceeded your threshold) disable it.

I think it's doable, but I have not had the need to accomplish this particular task.

Regards,

hmscott

I doubt it...since SQL Server "security" is not the way to go...you can "See" passwords as plain as day...oh, I forgot...M$ describes this as a feature....