How to create SQL Login audit log?

Hi, All
I use SQL Server 2000 and Win 2003 Server. I try to create a SQL Server
Login audit log using Profiler, but cannot find the tools. I looked at the
Windows Event Viewer, it only logs Windows authentications users for SQL
Server not SQL Server users (Mixed mode users).
Please help on creating SQL Server Login log (username,password and time).
Thanks
KaiHello,
SQL Profiler is a component of SQL Client Tools. Check if you have
installed SQL Client Tools on your server. By default, you can start SQL
Profiler by clicking Start > All Programs > Microsoft SQL Server >
Profiler.
To audit on successful login attempts or failed login attempts, you need to
select the option "Audit level: success" or "Audit level: failure" or
"Audit level: All" in the SQL Server Properties (Security Tab). You can
refer to the following information in the "SQL Server Properties (Security
Tab)" topic in SQL server Books Online(BOL):
All
Audit on both successful and failed login attempts. You can record
attempted user accesses as well as other SQL Server log information, and
enable auditing for both security modes, and you can record information on
both trusted and nontrusted connections. Log records for these events
appear in the Windows application log, the SQL Server error log, or both,
depending on how you configure logging for your SQL Server.
If you select this option, you must stop and restart the server to enable
auditing.
--
For more information, refer to the "SQL Server Properties (Security Tab)"
topic in BOL.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Guo,
Thanks for your help.
I setup "All" for Audit level in security, after that, in application
view, I restart SQL Server, I found user colum is "N/A" or "System". Any
thing I did not do?
Thanks
Kai
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:15x7bmQjFHA.588@.TK2MSFTNGXA01.phx.gbl...
> Hello,
> SQL Profiler is a component of SQL Client Tools. Check if you have
> installed SQL Client Tools on your server. By default, you can start SQL
> Profiler by clicking Start > All Programs > Microsoft SQL Server >
> Profiler.
> To audit on successful login attempts or failed login attempts, you need
> to
> select the option "Audit level: success" or "Audit level: failure" or
> "Audit level: All" in the SQL Server Properties (Security Tab). You can
> refer to the following information in the "SQL Server Properties (Security
> Tab)" topic in SQL server Books Online(BOL):
> --
> All
> Audit on both successful and failed login attempts. You can record
> attempted user accesses as well as other SQL Server log information, and
> enable auditing for both security modes, and you can record information on
> both trusted and nontrusted connections. Log records for these events
> appear in the Windows application log, the SQL Server error log, or both,
> depending on how you configure logging for your SQL Server.
> If you select this option, you must stop and restart the server to enable
> auditing.
> --
> For more information, refer to the "SQL Server Properties (Security Tab)"
> topic in BOL.
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>|||Hello,
User colum is "N/A" in application view of Event Viewer if you log on as a
SQL login. However, double-click the event , you may read the information
looks like the followings in the event properties:
18454 :
Login succeeded for user 'sa'. Connection: Non-Trusted.
18456 :
Login failed for user 'sa'.
or you can find the following information in the SQL logs:
2005-07-20 16:48:10.32 logon Login failed for user 'sa'.
2005-07-20 16:48:14.75 logon Login succeeded for user 'sa'. Connection:
Non-Trusted.
By default, the SQL logs located in the folder "C:\Program Files\Microsoft
SQL Server\MSSQL\LOG".
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

How to create Logs?

Can anyone please tell me where and how to configure SQL log files. I am a
Network Admin person and don't know anything in SQL.
Can you specify if its server error log file or database log file?
Thanks,
Sree
"iice" wrote:

> Can anyone please tell me where and how to configure SQL log files. I am a
> Network Admin person and don't know anything in SQL.
|||I want to know all the details of the database starting from accessing,
execution details, error logs etc. Is there any way of seeing? Pls do help me.
"Sreejith G" wrote:
[vbcol=seagreen]
> Can you specify if its server error log file or database log file?
> Thanks,
> Sree
> "iice" wrote:

How to create Logs?

Can anyone please tell me where and how to configure SQL log files. I am a
Network Admin person and don't know anything in SQL.Can you specify if its server error log file or database log file?
Thanks,
Sree
"iice" wrote:

> Can anyone please tell me where and how to configure SQL log files. I am a
> Network Admin person and don't know anything in SQL.|||I want to know all the details of the database starting from accessing,
execution details, error logs etc. Is there any way of seeing? Pls do help m
e.
"Sreejith G" wrote:
[vbcol=seagreen]
> Can you specify if its server error log file or database log file?
> Thanks,
> Sree
> "iice" wrote:
>sql

How to create Logs?

Can anyone please tell me where and how to configure SQL log files. I am a
Network Admin person and don't know anything in SQL.Can you specify if its server error log file or database log file?
Thanks,
Sree
"iice" wrote:
> Can anyone please tell me where and how to configure SQL log files. I am a
> Network Admin person and don't know anything in SQL.|||I want to know all the details of the database starting from accessing,
execution details, error logs etc. Is there any way of seeing? Pls do help me.
"Sreejith G" wrote:
> Can you specify if its server error log file or database log file?
> Thanks,
> Sree
> "iice" wrote:
> > Can anyone please tell me where and how to configure SQL log files. I am a
> > Network Admin person and don't know anything in SQL.

How to corrupt data

Hello!
I'm intresed in all possible ways to corrupt data and log files in SQL Server 2000 except manually editing them.
Thank you in advance.you can hurt peaple more directly if that what you want|||Damn!

I'm not intrested in hurting anyone!
On the opposite - I work in QA team for the company that makes disaster recovery software for various databases. I need this information in order to test our product.|||So what you are really saying is that you need help doing your job.|||Correct! And I'm not ashamed of it. This is not a kind of information you can find in books or manuals.

How to correct registry in renamed server

If a log shipping server must take on the name of another server during
failover, the name in the server registry will not be the same as the name of
the server. What is the best way to correct this?
Regards,
Jamie
Found it
SQL Server 2000
sp_dropserver 'old server name'
sp_addserver 'new server name', 'local'
Delete the entry in Enterprise Manager for the old server name and then
you’re golden. You will have to stop and start the SQL Server service to
complete the process.
Regards,
Jamie
"thejamie" wrote:

> If a log shipping server must take on the name of another server during
> failover, the name in the server registry will not be the same as the name of
> the server. What is the best way to correct this?
> --
> Regards,
> Jamie
|||And if you are on 2000, you need to handle the Agent jobs as well:
http://www.karaszi.com/SQLServer/info_change_server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:DFACE678-CD17-4B17-9E15-D5FDC74A0A2C@.microsoft.com...[vbcol=seagreen]
> Found it
> SQL Server 2000
> sp_dropserver 'old server name'
> sp_addserver 'new server name', 'local'
> Delete the entry in Enterprise Manager for the old server name and then
> you’re golden. You will have to stop and start the SQL Server service to
> complete the process.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:

How to correct registry in renamed server

If a log shipping server must take on the name of another server during
failover, the name in the server registry will not be the same as the name o
f
the server. What is the best way to correct this?
--
Regards,
JamieFound it
SQL Server 2000
sp_dropserver 'old server name'
sp_addserver 'new server name', 'local'
Delete the entry in Enterprise Manager for the old server name and then
you’re golden. You will have to stop and start the SQL Server service to
complete the process.
--
Regards,
Jamie
"thejamie" wrote:

> If a log shipping server must take on the name of another server during
> failover, the name in the server registry will not be the same as the name
of
> the server. What is the best way to correct this?
> --
> Regards,
> Jamie|||And if you are on 2000, you need to handle the Agent jobs as well:
http://www.karaszi.com/SQLServer/in...server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:DFACE678-CD17-4B17-9E15-D5FDC74A0A2C@.microsoft.com...[vbcol=seagreen]
> Found it
> SQL Server 2000
> sp_dropserver 'old server name'
> sp_addserver 'new server name', 'local'
> Delete the entry in Enterprise Manager for the old server name and then
> you’re golden. You will have to stop and start the SQL Server service to
> complete the process.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:
>

How to correct registry in renamed server

If a log shipping server must take on the name of another server during
failover, the name in the server registry will not be the same as the name of
the server. What is the best way to correct this?
--
Regards,
JamieFound it
SQL Server 2000
sp_dropserver 'old server name'
sp_addserver 'new server name', 'local'
Delete the entry in Enterprise Manager for the old server name and then
youâ're golden. You will have to stop and start the SQL Server service to
complete the process.
--
Regards,
Jamie
"thejamie" wrote:
> If a log shipping server must take on the name of another server during
> failover, the name in the server registry will not be the same as the name of
> the server. What is the best way to correct this?
> --
> Regards,
> Jamie|||And if you are on 2000, you need to handle the Agent jobs as well:
http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:DFACE678-CD17-4B17-9E15-D5FDC74A0A2C@.microsoft.com...
> Found it
> SQL Server 2000
> sp_dropserver 'old server name'
> sp_addserver 'new server name', 'local'
> Delete the entry in Enterprise Manager for the old server name and then
> youâ're golden. You will have to stop and start the SQL Server service to
> complete the process.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:
>> If a log shipping server must take on the name of another server during
>> failover, the name in the server registry will not be the same as the name of
>> the server. What is the best way to correct this?
>> --
>> Regards,
>> Jamie