Dear all
My one user has installed sql server 2000 enterprise edition , SP3
(8.00.0860) on my computer.
I have created one odbc connection to sql server.
When he want to connect to sql user via odbc in application he gets
following error
Statement(s) could not be prepared
Unable to close cursor
[Microsoft][ODBC SQL Server Driver]Invalid cursor stat
What can be the problem?
RegardsWhat language is the application written in? At least the failing module?
I have seen similar errors in both T/SQL (implying a Stored Procedure) and C
(api level calls) modules.
I suspect it needs to be relinked with your new modules. To me, it sounds
like the api calls either are for a different ODBC release or have messed up
pointers.
If you can supply error numbers and complete error messages, it woulld help
--
Joseph R.P. Maloney, CSP,CCP,CDP
"amish" wrote:
> Dear all
> My one user has installed sql server 2000 enterprise edition , SP3
> (8.00.0860) on my computer.
> I have created one odbc connection to sql server.
> When he want to connect to sql user via odbc in application he gets
> following error
> Statement(s) could not be prepared
> Unable to close cursor
> [Microsoft][ODBC SQL Server Driver]Invalid cursor stat
> What can be the problem?
> Regards
>
Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
ODBC Drive Memory Leak
I have experienced the ODBC Driver memory leak problem
described in KB814410 with SP3, and had to back-out of SP3
because of it. I see there is a fix though it appears I
have to go through MS support to get it. Trouble is, the
support wizard won't take my VALID SQL Server registration
number.
Do I need to use one of my MSDN support incidents to get
this?
ThanksI've had to call in to support for a SQL hotfix before
using an MSDN support incident. If they determine your
problem is fixed by the hotfix they will credit you the
support incident or credit card payment you have made.
-Aaron
>--Original Message--
>I have experienced the ODBC Driver memory leak problem
>described in KB814410 with SP3, and had to back-out of
SP3
>because of it. I see there is a fix though it appears I
>have to go through MS support to get it. Trouble is, the
>support wizard won't take my VALID SQL Server
registration
>number.
>Do I need to use one of my MSDN support incidents to get
>this?
>Thanks
>
>.
>
described in KB814410 with SP3, and had to back-out of SP3
because of it. I see there is a fix though it appears I
have to go through MS support to get it. Trouble is, the
support wizard won't take my VALID SQL Server registration
number.
Do I need to use one of my MSDN support incidents to get
this?
ThanksI've had to call in to support for a SQL hotfix before
using an MSDN support incident. If they determine your
problem is fixed by the hotfix they will credit you the
support incident or credit card payment you have made.
-Aaron
>--Original Message--
>I have experienced the ODBC Driver memory leak problem
>described in KB814410 with SP3, and had to back-out of
SP3
>because of it. I see there is a fix though it appears I
>have to go through MS support to get it. Trouble is, the
>support wizard won't take my VALID SQL Server
registration
>number.
>Do I need to use one of my MSDN support incidents to get
>this?
>Thanks
>
>.
>
Wednesday, March 21, 2012
ODBC connection fails
I'm running SQL 2000/SP3 on a W2k server. I have a database with a standard
user (dbo rights). From any of my workstations I can create an ODBC
connection using SQL authentication.
When I try to create an ODBC connection on the server itself with the same
credentials, I get an error msg "login failed, username is not associated
with a trusted server connection". Using Windows authentication with another
user that has access to the SQL server works fine.
This doesn't make sense to me. What am I overlooking here? Any help/hint
would be appreciated.
Thanks
Claus"cjobes" <cjobes@.nova-tech.org> wrote in message
news:O6t6OxyBEHA.3928@.TK2MSFTNGP11.phx.gbl...
> I'm running SQL 2000/SP3 on a W2k server. I have a database with a
standard
> user (dbo rights). From any of my workstations I can create an ODBC
> connection using SQL authentication.
> When I try to create an ODBC connection on the server itself with the same
> credentials, I get an error msg "login failed, username is not associated
> with a trusted server connection". Using Windows authentication with
another
> user that has access to the SQL server works fine.
> This doesn't make sense to me. What am I overlooking here? Any help/hint
> would be appreciated.
The user account itself needs to have access to the server running SQL
Server. One way to verify, temporarily enable (don't leave it that way ;)
the server GUEST account.
Steve|||Hello,
Define user id "sa" and set pwd for sa account on sql server and try to
login that account on odbc connection.
i hope it will working fine.
Thanks,
Warm Regards,
Ayaz Ahmed
Software Engineer & Web Developer
Creative Chaos (Pvt.) Ltd.
"Managing Your Digital Risk"
http://www.csquareonline.com
Karachi, Pakistan
Mobile +92 300 2280950
Office +92 21 455 2414
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Actually that is a not a good idea (at least as a permanent solution) as sql
security is sent over the network in clear text.
Steve
"Ayaz Ahmed" <ayaz@.csquareonline.com> wrote in message
news:e4EAqBkDEHA.2712@.TK2MSFTNGP10.phx.gbl...
> Hello,
> Define user id "sa" and set pwd for sa account on sql server and try to
> login that account on odbc connection.
> i hope it will working fine.
>
> Thanks,
> Warm Regards,
> Ayaz Ahmed
> Software Engineer & Web Developer
> Creative Chaos (Pvt.) Ltd.
> "Managing Your Digital Risk"
> http://www.csquareonline.com
> Karachi, Pakistan
> Mobile +92 300 2280950
> Office +92 21 455 2414
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!
user (dbo rights). From any of my workstations I can create an ODBC
connection using SQL authentication.
When I try to create an ODBC connection on the server itself with the same
credentials, I get an error msg "login failed, username is not associated
with a trusted server connection". Using Windows authentication with another
user that has access to the SQL server works fine.
This doesn't make sense to me. What am I overlooking here? Any help/hint
would be appreciated.
Thanks
Claus"cjobes" <cjobes@.nova-tech.org> wrote in message
news:O6t6OxyBEHA.3928@.TK2MSFTNGP11.phx.gbl...
> I'm running SQL 2000/SP3 on a W2k server. I have a database with a
standard
> user (dbo rights). From any of my workstations I can create an ODBC
> connection using SQL authentication.
> When I try to create an ODBC connection on the server itself with the same
> credentials, I get an error msg "login failed, username is not associated
> with a trusted server connection". Using Windows authentication with
another
> user that has access to the SQL server works fine.
> This doesn't make sense to me. What am I overlooking here? Any help/hint
> would be appreciated.
The user account itself needs to have access to the server running SQL
Server. One way to verify, temporarily enable (don't leave it that way ;)
the server GUEST account.
Steve|||Hello,
Define user id "sa" and set pwd for sa account on sql server and try to
login that account on odbc connection.
i hope it will working fine.
Thanks,
Warm Regards,
Ayaz Ahmed
Software Engineer & Web Developer
Creative Chaos (Pvt.) Ltd.
"Managing Your Digital Risk"
http://www.csquareonline.com
Karachi, Pakistan
Mobile +92 300 2280950
Office +92 21 455 2414
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Actually that is a not a good idea (at least as a permanent solution) as sql
security is sent over the network in clear text.
Steve
"Ayaz Ahmed" <ayaz@.csquareonline.com> wrote in message
news:e4EAqBkDEHA.2712@.TK2MSFTNGP10.phx.gbl...
> Hello,
> Define user id "sa" and set pwd for sa account on sql server and try to
> login that account on odbc connection.
> i hope it will working fine.
>
> Thanks,
> Warm Regards,
> Ayaz Ahmed
> Software Engineer & Web Developer
> Creative Chaos (Pvt.) Ltd.
> "Managing Your Digital Risk"
> http://www.csquareonline.com
> Karachi, Pakistan
> Mobile +92 300 2280950
> Office +92 21 455 2414
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!
Friday, February 24, 2012
Obtain Info
Hi
I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
major information from log file, i.e. if a user loggin to db i want know the
time/date to login, operation excute etc.
Can help me please
Tia Pupo
Hi
Logins/Logout can be logged into the SQL Event log, but what the user
executed, you need to use Profiler for that.
Generally, for SOX compliance, people run Profiler to capture all the events
and use that to report on.
Regards
Mike
"Pupo" wrote:
> Hi
> I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
> major information from log file, i.e. if a user loggin to db i want know the
> time/date to login, operation excute etc.
> Can help me please
> Tia Pupo
>
>
|||Hi,
How to Enable the Audit for Logins:-
SQL 2000 - Open enterprise manager -- Right click on server and select
properties and then choose the Security tab and
select Audit level "ALL" and click Ok and restart SQL server service.
Operation excuted: These information can not be looged into the SQL Server
error log. But you could create the trace and schedule it to
run and log to a file. See the commands
sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
Thanks
Hari
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...[vbcol=seagreen]
> Hi
> Logins/Logout can be logged into the SQL Event log, but what the user
> executed, you need to use Profiler for that.
> Generally, for SOX compliance, people run Profiler to capture all the
> events
> and use that to report on.
> Regards
> Mike
> "Pupo" wrote:
|||Thanks i try it, in others newsgroup tell me about specific programm to
monitorate log as "log explorer" someone have use it before?
Tia
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Hi,
> How to Enable the Audit for Logins:-
> --
> SQL 2000 - Open enterprise manager -- Right click on server and select
> properties and then choose the Security tab and
> select Audit level "ALL" and click Ok and restart SQL server service.
>
> Operation excuted: These information can not be looged into the SQL Server
> error log. But you could create the trace and schedule it to
> run and log to a file. See the commands
> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> Thanks
> Hari
> SQL Server MVP
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
know
>
|||Sounds like you are asking about this product:
http://www.lumigent.com/products/le_sql.html
It works quite well.
Steve
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
Server
> know
>
|||Hi,
You can also use Log explorer from Lumigent. Great tool to read the
transaction logs. Try it out from:-
www.Lumigent.com
Thanks
Hari
SQL Server MVP
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> know
>
|||Hi
Those log reader tools only can report on what was changed. If someone ran a
SELECT, it is not logged as non-data monification statements are not logged
into the transaction log.
SQL Server Profiler/Trace is the only tool that will report on everything
that is going in and out the server.
Regards
Mike
"Hari Prasad" wrote:
> Hi,
> You can also use Log explorer from Lumigent. Great tool to read the
> transaction logs. Try it out from:-
> www.Lumigent.com
> Thanks
> Hari
> SQL Server MVP
> "Pupo" <123star@.libero.it> wrote in message
> news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
>
>
I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
major information from log file, i.e. if a user loggin to db i want know the
time/date to login, operation excute etc.
Can help me please
Tia Pupo
Hi
Logins/Logout can be logged into the SQL Event log, but what the user
executed, you need to use Profiler for that.
Generally, for SOX compliance, people run Profiler to capture all the events
and use that to report on.
Regards
Mike
"Pupo" wrote:
> Hi
> I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
> major information from log file, i.e. if a user loggin to db i want know the
> time/date to login, operation excute etc.
> Can help me please
> Tia Pupo
>
>
|||Hi,
How to Enable the Audit for Logins:-
SQL 2000 - Open enterprise manager -- Right click on server and select
properties and then choose the Security tab and
select Audit level "ALL" and click Ok and restart SQL server service.
Operation excuted: These information can not be looged into the SQL Server
error log. But you could create the trace and schedule it to
run and log to a file. See the commands
sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
Thanks
Hari
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...[vbcol=seagreen]
> Hi
> Logins/Logout can be logged into the SQL Event log, but what the user
> executed, you need to use Profiler for that.
> Generally, for SOX compliance, people run Profiler to capture all the
> events
> and use that to report on.
> Regards
> Mike
> "Pupo" wrote:
|||Thanks i try it, in others newsgroup tell me about specific programm to
monitorate log as "log explorer" someone have use it before?
Tia
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Hi,
> How to Enable the Audit for Logins:-
> --
> SQL 2000 - Open enterprise manager -- Right click on server and select
> properties and then choose the Security tab and
> select Audit level "ALL" and click Ok and restart SQL server service.
>
> Operation excuted: These information can not be looged into the SQL Server
> error log. But you could create the trace and schedule it to
> run and log to a file. See the commands
> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> Thanks
> Hari
> SQL Server MVP
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
know
>
|||Sounds like you are asking about this product:
http://www.lumigent.com/products/le_sql.html
It works quite well.
Steve
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
Server
> know
>
|||Hi,
You can also use Log explorer from Lumigent. Great tool to read the
transaction logs. Try it out from:-
www.Lumigent.com
Thanks
Hari
SQL Server MVP
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> know
>
|||Hi
Those log reader tools only can report on what was changed. If someone ran a
SELECT, it is not logged as non-data monification statements are not logged
into the transaction log.
SQL Server Profiler/Trace is the only tool that will report on everything
that is going in and out the server.
Regards
Mike
"Hari Prasad" wrote:
> Hi,
> You can also use Log explorer from Lumigent. Great tool to read the
> transaction logs. Try it out from:-
> www.Lumigent.com
> Thanks
> Hari
> SQL Server MVP
> "Pupo" <123star@.libero.it> wrote in message
> news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
>
>
Obtain Info
Hi
I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
major information from log file, i.e. if a user loggin to db i want know the
time/date to login, operation excute etc.
Can help me please
Tia Pupo
Hi
Logins/Logout can be logged into the SQL Event log, but what the user
executed, you need to use Profiler for that.
Generally, for SOX compliance, people run Profiler to capture all the events
and use that to report on.
Regards
Mike
"Pupo" wrote:
> Hi
> I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
> major information from log file, i.e. if a user loggin to db i want know the
> time/date to login, operation excute etc.
> Can help me please
> Tia Pupo
>
>
|||Hi,
How to Enable the Audit for Logins:-
SQL 2000 - Open enterprise manager -- Right click on server and select
properties and then choose the Security tab and
select Audit level "ALL" and click Ok and restart SQL server service.
Operation excuted: These information can not be looged into the SQL Server
error log. But you could create the trace and schedule it to
run and log to a file. See the commands
sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
Thanks
Hari
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...[vbcol=seagreen]
> Hi
> Logins/Logout can be logged into the SQL Event log, but what the user
> executed, you need to use Profiler for that.
> Generally, for SOX compliance, people run Profiler to capture all the
> events
> and use that to report on.
> Regards
> Mike
> "Pupo" wrote:
|||Thanks i try it, in others newsgroup tell me about specific programm to
monitorate log as "log explorer" someone have use it before?
Tia
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Hi,
> How to Enable the Audit for Logins:-
> --
> SQL 2000 - Open enterprise manager -- Right click on server and select
> properties and then choose the Security tab and
> select Audit level "ALL" and click Ok and restart SQL server service.
>
> Operation excuted: These information can not be looged into the SQL Server
> error log. But you could create the trace and schedule it to
> run and log to a file. See the commands
> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> Thanks
> Hari
> SQL Server MVP
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
know
>
|||Sounds like you are asking about this product:
http://www.lumigent.com/products/le_sql.html
It works quite well.
Steve
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
Server
> know
>
|||Hi,
You can also use Log explorer from Lumigent. Great tool to read the
transaction logs. Try it out from:-
www.Lumigent.com
Thanks
Hari
SQL Server MVP
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> know
>
|||Hi
Those log reader tools only can report on what was changed. If someone ran a
SELECT, it is not logged as non-data monification statements are not logged
into the transaction log.
SQL Server Profiler/Trace is the only tool that will report on everything
that is going in and out the server.
Regards
Mike
"Hari Prasad" wrote:
> Hi,
> You can also use Log explorer from Lumigent. Great tool to read the
> transaction logs. Try it out from:-
> www.Lumigent.com
> Thanks
> Hari
> SQL Server MVP
> "Pupo" <123star@.libero.it> wrote in message
> news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
>
>
I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
major information from log file, i.e. if a user loggin to db i want know the
time/date to login, operation excute etc.
Can help me please
Tia Pupo
Hi
Logins/Logout can be logged into the SQL Event log, but what the user
executed, you need to use Profiler for that.
Generally, for SOX compliance, people run Profiler to capture all the events
and use that to report on.
Regards
Mike
"Pupo" wrote:
> Hi
> I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
> major information from log file, i.e. if a user loggin to db i want know the
> time/date to login, operation excute etc.
> Can help me please
> Tia Pupo
>
>
|||Hi,
How to Enable the Audit for Logins:-
SQL 2000 - Open enterprise manager -- Right click on server and select
properties and then choose the Security tab and
select Audit level "ALL" and click Ok and restart SQL server service.
Operation excuted: These information can not be looged into the SQL Server
error log. But you could create the trace and schedule it to
run and log to a file. See the commands
sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
Thanks
Hari
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...[vbcol=seagreen]
> Hi
> Logins/Logout can be logged into the SQL Event log, but what the user
> executed, you need to use Profiler for that.
> Generally, for SOX compliance, people run Profiler to capture all the
> events
> and use that to report on.
> Regards
> Mike
> "Pupo" wrote:
|||Thanks i try it, in others newsgroup tell me about specific programm to
monitorate log as "log explorer" someone have use it before?
Tia
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Hi,
> How to Enable the Audit for Logins:-
> --
> SQL 2000 - Open enterprise manager -- Right click on server and select
> properties and then choose the Security tab and
> select Audit level "ALL" and click Ok and restart SQL server service.
>
> Operation excuted: These information can not be looged into the SQL Server
> error log. But you could create the trace and schedule it to
> run and log to a file. See the commands
> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> Thanks
> Hari
> SQL Server MVP
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
know
>
|||Sounds like you are asking about this product:
http://www.lumigent.com/products/le_sql.html
It works quite well.
Steve
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
Server
> know
>
|||Hi,
You can also use Log explorer from Lumigent. Great tool to read the
transaction logs. Try it out from:-
www.Lumigent.com
Thanks
Hari
SQL Server MVP
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> know
>
|||Hi
Those log reader tools only can report on what was changed. If someone ran a
SELECT, it is not logged as non-data monification statements are not logged
into the transaction log.
SQL Server Profiler/Trace is the only tool that will report on everything
that is going in and out the server.
Regards
Mike
"Hari Prasad" wrote:
> Hi,
> You can also use Log explorer from Lumigent. Great tool to read the
> transaction logs. Try it out from:-
> www.Lumigent.com
> Thanks
> Hari
> SQL Server MVP
> "Pupo" <123star@.libero.it> wrote in message
> news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
>
>
Obtain Info
Hi
I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
major information from log file, i.e. if a user loggin to db i want know the
time/date to login, operation excute etc.
Can help me please
Tia Pupo
Hi
Logins/Logout can be logged into the SQL Event log, but what the user
executed, you need to use Profiler for that.
Generally, for SOX compliance, people run Profiler to capture all the events
and use that to report on.
Regards
Mike
"Pupo" wrote:
> Hi
> I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
> major information from log file, i.e. if a user loggin to db i want know the
> time/date to login, operation excute etc.
> Can help me please
> Tia Pupo
>
>
|||Hi,
How to Enable the Audit for Logins:-
SQL 2000 - Open enterprise manager -- Right click on server and select
properties and then choose the Security tab and
select Audit level "ALL" and click Ok and restart SQL server service.
Operation excuted: These information can not be looged into the SQL Server
error log. But you could create the trace and schedule it to
run and log to a file. See the commands
sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
Thanks
Hari
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...[vbcol=seagreen]
> Hi
> Logins/Logout can be logged into the SQL Event log, but what the user
> executed, you need to use Profiler for that.
> Generally, for SOX compliance, people run Profiler to capture all the
> events
> and use that to report on.
> Regards
> Mike
> "Pupo" wrote:
|||Thanks i try it, in others newsgroup tell me about specific programm to
monitorate log as "log explorer" someone have use it before?
Tia
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Hi,
> How to Enable the Audit for Logins:-
> --
> SQL 2000 - Open enterprise manager -- Right click on server and select
> properties and then choose the Security tab and
> select Audit level "ALL" and click Ok and restart SQL server service.
>
> Operation excuted: These information can not be looged into the SQL Server
> error log. But you could create the trace and schedule it to
> run and log to a file. See the commands
> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> Thanks
> Hari
> SQL Server MVP
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
know
>
|||Sounds like you are asking about this product:
http://www.lumigent.com/products/le_sql.html
It works quite well.
Steve
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
Server
> know
>
|||Hi,
You can also use Log explorer from Lumigent. Great tool to read the
transaction logs. Try it out from:-
www.Lumigent.com
Thanks
Hari
SQL Server MVP
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> know
>
|||Hi
Those log reader tools only can report on what was changed. If someone ran a
SELECT, it is not logged as non-data monification statements are not logged
into the transaction log.
SQL Server Profiler/Trace is the only tool that will report on everything
that is going in and out the server.
Regards
Mike
"Hari Prasad" wrote:
> Hi,
> You can also use Log explorer from Lumigent. Great tool to read the
> transaction logs. Try it out from:-
> www.Lumigent.com
> Thanks
> Hari
> SQL Server MVP
> "Pupo" <123star@.libero.it> wrote in message
> news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
>
>
I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
major information from log file, i.e. if a user loggin to db i want know the
time/date to login, operation excute etc.
Can help me please
Tia Pupo
Hi
Logins/Logout can be logged into the SQL Event log, but what the user
executed, you need to use Profiler for that.
Generally, for SOX compliance, people run Profiler to capture all the events
and use that to report on.
Regards
Mike
"Pupo" wrote:
> Hi
> I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
> major information from log file, i.e. if a user loggin to db i want know the
> time/date to login, operation excute etc.
> Can help me please
> Tia Pupo
>
>
|||Hi,
How to Enable the Audit for Logins:-
SQL 2000 - Open enterprise manager -- Right click on server and select
properties and then choose the Security tab and
select Audit level "ALL" and click Ok and restart SQL server service.
Operation excuted: These information can not be looged into the SQL Server
error log. But you could create the trace and schedule it to
run and log to a file. See the commands
sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
Thanks
Hari
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...[vbcol=seagreen]
> Hi
> Logins/Logout can be logged into the SQL Event log, but what the user
> executed, you need to use Profiler for that.
> Generally, for SOX compliance, people run Profiler to capture all the
> events
> and use that to report on.
> Regards
> Mike
> "Pupo" wrote:
|||Thanks i try it, in others newsgroup tell me about specific programm to
monitorate log as "log explorer" someone have use it before?
Tia
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Hi,
> How to Enable the Audit for Logins:-
> --
> SQL 2000 - Open enterprise manager -- Right click on server and select
> properties and then choose the Security tab and
> select Audit level "ALL" and click Ok and restart SQL server service.
>
> Operation excuted: These information can not be looged into the SQL Server
> error log. But you could create the trace and schedule it to
> run and log to a file. See the commands
> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> Thanks
> Hari
> SQL Server MVP
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
know
>
|||Sounds like you are asking about this product:
http://www.lumigent.com/products/le_sql.html
It works quite well.
Steve
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
Server
> know
>
|||Hi,
You can also use Log explorer from Lumigent. Great tool to read the
transaction logs. Try it out from:-
www.Lumigent.com
Thanks
Hari
SQL Server MVP
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> know
>
|||Hi
Those log reader tools only can report on what was changed. If someone ran a
SELECT, it is not logged as non-data monification statements are not logged
into the transaction log.
SQL Server Profiler/Trace is the only tool that will report on everything
that is going in and out the server.
Regards
Mike
"Hari Prasad" wrote:
> Hi,
> You can also use Log explorer from Lumigent. Great tool to read the
> transaction logs. Try it out from:-
> www.Lumigent.com
> Thanks
> Hari
> SQL Server MVP
> "Pupo" <123star@.libero.it> wrote in message
> news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
>
>
Obtain Info
Hi
I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
major information from log file, i.e. if a user loggin to db i want know the
time/date to login, operation excute etc.
Can help me please
Tia PupoHi
Logins/Logout can be logged into the SQL Event log, but what the user
executed, you need to use Profiler for that.
Generally, for SOX compliance, people run Profiler to capture all the events
and use that to report on.
Regards
Mike
"Pupo" wrote:
> Hi
> I have SQL 2000 server Sp3 on my network, i want know if is possible obta
in
> major information from log file, i.e. if a user loggin to db i want know t
he
> time/date to login, operation excute etc.
> Can help me please
> Tia Pupo
>
>|||Hi,
How to Enable the Audit for Logins:-
--
SQL 2000 - Open enterprise manager -- Right click on server and select
properties and then choose the Security tab and
select Audit level "ALL" and click Ok and restart SQL server service.
Operation excuted: These information can not be looged into the SQL Server
error log. But you could create the trace and schedule it to
run and log to a file. See the commands
sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
Thanks
Hari
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...[vbcol=seagreen]
> Hi
> Logins/Logout can be logged into the SQL Event log, but what the user
> executed, you need to use Profiler for that.
> Generally, for SOX compliance, people run Profiler to capture all the
> events
> and use that to report on.
> Regards
> Mike
> "Pupo" wrote:
>|||Thanks i try it, in others newsgroup tell me about specific programm to
monitorate log as "log explorer" someone have use it before?
Tia
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> Hi,
> How to Enable the Audit for Logins:-
> --
> SQL 2000 - Open enterprise manager -- Right click on server and select
> properties and then choose the Security tab and
> select Audit level "ALL" and click Ok and restart SQL server service.
>
> Operation excuted: These information can not be looged into the SQL Server
> error log. But you could create the trace and schedule it to
> run and log to a file. See the commands
> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> Thanks
> Hari
> SQL Server MVP
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
know[vbcol=seagreen]
>|||Sounds like you are asking about this product:
http://www.lumigent.com/products/le_sql.html
It works quite well.
Steve
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
Server[vbcol=seagreen]
> know
>|||Hi,
You can also use Log explorer from Lumigent. Great tool to read the
transaction logs. Try it out from:-
www.Lumigent.com
Thanks
Hari
SQL Server MVP
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> know
>|||Hi
Those log reader tools only can report on what was changed. If someone ran a
SELECT, it is not logged as non-data monification statements are not logged
into the transaction log.
SQL Server Profiler/Trace is the only tool that will report on everything
that is going in and out the server.
Regards
Mike
"Hari Prasad" wrote:
> Hi,
> You can also use Log explorer from Lumigent. Great tool to read the
> transaction logs. Try it out from:-
> www.Lumigent.com
> Thanks
> Hari
> SQL Server MVP
> "Pupo" <123star@.libero.it> wrote in message
> news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
>
>
I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
major information from log file, i.e. if a user loggin to db i want know the
time/date to login, operation excute etc.
Can help me please
Tia PupoHi
Logins/Logout can be logged into the SQL Event log, but what the user
executed, you need to use Profiler for that.
Generally, for SOX compliance, people run Profiler to capture all the events
and use that to report on.
Regards
Mike
"Pupo" wrote:
> Hi
> I have SQL 2000 server Sp3 on my network, i want know if is possible obta
in
> major information from log file, i.e. if a user loggin to db i want know t
he
> time/date to login, operation excute etc.
> Can help me please
> Tia Pupo
>
>|||Hi,
How to Enable the Audit for Logins:-
--
SQL 2000 - Open enterprise manager -- Right click on server and select
properties and then choose the Security tab and
select Audit level "ALL" and click Ok and restart SQL server service.
Operation excuted: These information can not be looged into the SQL Server
error log. But you could create the trace and schedule it to
run and log to a file. See the commands
sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
Thanks
Hari
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...[vbcol=seagreen]
> Hi
> Logins/Logout can be logged into the SQL Event log, but what the user
> executed, you need to use Profiler for that.
> Generally, for SOX compliance, people run Profiler to capture all the
> events
> and use that to report on.
> Regards
> Mike
> "Pupo" wrote:
>|||Thanks i try it, in others newsgroup tell me about specific programm to
monitorate log as "log explorer" someone have use it before?
Tia
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> Hi,
> How to Enable the Audit for Logins:-
> --
> SQL 2000 - Open enterprise manager -- Right click on server and select
> properties and then choose the Security tab and
> select Audit level "ALL" and click Ok and restart SQL server service.
>
> Operation excuted: These information can not be looged into the SQL Server
> error log. But you could create the trace and schedule it to
> run and log to a file. See the commands
> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> Thanks
> Hari
> SQL Server MVP
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
know[vbcol=seagreen]
>|||Sounds like you are asking about this product:
http://www.lumigent.com/products/le_sql.html
It works quite well.
Steve
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
Server[vbcol=seagreen]
> know
>|||Hi,
You can also use Log explorer from Lumigent. Great tool to read the
transaction logs. Try it out from:-
www.Lumigent.com
Thanks
Hari
SQL Server MVP
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> know
>|||Hi
Those log reader tools only can report on what was changed. If someone ran a
SELECT, it is not logged as non-data monification statements are not logged
into the transaction log.
SQL Server Profiler/Trace is the only tool that will report on everything
that is going in and out the server.
Regards
Mike
"Hari Prasad" wrote:
> Hi,
> You can also use Log explorer from Lumigent. Great tool to read the
> transaction logs. Try it out from:-
> www.Lumigent.com
> Thanks
> Hari
> SQL Server MVP
> "Pupo" <123star@.libero.it> wrote in message
> news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
>
>
Obtain Info
Hi
I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
major information from log file, i.e. if a user loggin to db i want know the
time/date to login, operation excute etc.
Can help me please
Tia PupoHi
Logins/Logout can be logged into the SQL Event log, but what the user
executed, you need to use Profiler for that.
Generally, for SOX compliance, people run Profiler to capture all the events
and use that to report on.
Regards
Mike
"Pupo" wrote:
> Hi
> I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
> major information from log file, i.e. if a user loggin to db i want know the
> time/date to login, operation excute etc.
> Can help me please
> Tia Pupo
>
>|||Hi,
How to Enable the Audit for Logins:-
--
SQL 2000 - Open enterprise manager -- Right click on server and select
properties and then choose the Security tab and
select Audit level "ALL" and click Ok and restart SQL server service.
Operation excuted: These information can not be looged into the SQL Server
error log. But you could create the trace and schedule it to
run and log to a file. See the commands
sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
Thanks
Hari
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
> Hi
> Logins/Logout can be logged into the SQL Event log, but what the user
> executed, you need to use Profiler for that.
> Generally, for SOX compliance, people run Profiler to capture all the
> events
> and use that to report on.
> Regards
> Mike
> "Pupo" wrote:
>> Hi
>> I have SQL 2000 server Sp3 on my network, i want know if is possible
>> obtain
>> major information from log file, i.e. if a user loggin to db i want know
>> the
>> time/date to login, operation excute etc.
>> Can help me please
>> Tia Pupo
>>|||Thanks i try it, in others newsgroup tell me about specific programm to
monitorate log as "log explorer" someone have use it before?
Tia
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> Hi,
> How to Enable the Audit for Logins:-
> --
> SQL 2000 - Open enterprise manager -- Right click on server and select
> properties and then choose the Security tab and
> select Audit level "ALL" and click Ok and restart SQL server service.
>
> Operation excuted: These information can not be looged into the SQL Server
> error log. But you could create the trace and schedule it to
> run and log to a file. See the commands
> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> Thanks
> Hari
> SQL Server MVP
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
> > Hi
> >
> > Logins/Logout can be logged into the SQL Event log, but what the user
> > executed, you need to use Profiler for that.
> >
> > Generally, for SOX compliance, people run Profiler to capture all the
> > events
> > and use that to report on.
> >
> > Regards
> > Mike
> >
> > "Pupo" wrote:
> >
> >> Hi
> >> I have SQL 2000 server Sp3 on my network, i want know if is possible
> >> obtain
> >> major information from log file, i.e. if a user loggin to db i want
know
> >> the
> >> time/date to login, operation excute etc.
> >> Can help me please
> >> Tia Pupo
> >>
> >>
> >>
>|||Sounds like you are asking about this product:
http://www.lumigent.com/products/le_sql.html
It works quite well.
Steve
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > How to Enable the Audit for Logins:-
> > --
> > SQL 2000 - Open enterprise manager -- Right click on server and select
> > properties and then choose the Security tab and
> >
> > select Audit level "ALL" and click Ok and restart SQL server service.
> >
> >
> > Operation excuted: These information can not be looged into the SQL
Server
> > error log. But you could create the trace and schedule it to
> >
> > run and log to a file. See the commands
> >
> > sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> >
> > Thanks
> >
> > Hari
> >
> > SQL Server MVP
> >
> >
> > "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> > news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
> > > Hi
> > >
> > > Logins/Logout can be logged into the SQL Event log, but what the user
> > > executed, you need to use Profiler for that.
> > >
> > > Generally, for SOX compliance, people run Profiler to capture all the
> > > events
> > > and use that to report on.
> > >
> > > Regards
> > > Mike
> > >
> > > "Pupo" wrote:
> > >
> > >> Hi
> > >> I have SQL 2000 server Sp3 on my network, i want know if is possible
> > >> obtain
> > >> major information from log file, i.e. if a user loggin to db i want
> know
> > >> the
> > >> time/date to login, operation excute etc.
> > >> Can help me please
> > >> Tia Pupo
> > >>
> > >>
> > >>
> >
> >
>|||Hi,
You can also use Log explorer from Lumigent. Great tool to read the
transaction logs. Try it out from:-
www.Lumigent.com
Thanks
Hari
SQL Server MVP
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
>> Hi,
>> How to Enable the Audit for Logins:-
>> --
>> SQL 2000 - Open enterprise manager -- Right click on server and select
>> properties and then choose the Security tab and
>> select Audit level "ALL" and click Ok and restart SQL server service.
>>
>> Operation excuted: These information can not be looged into the SQL
>> Server
>> error log. But you could create the trace and schedule it to
>> run and log to a file. See the commands
>> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
>> Thanks
>> Hari
>> SQL Server MVP
>>
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
>> > Hi
>> >
>> > Logins/Logout can be logged into the SQL Event log, but what the user
>> > executed, you need to use Profiler for that.
>> >
>> > Generally, for SOX compliance, people run Profiler to capture all the
>> > events
>> > and use that to report on.
>> >
>> > Regards
>> > Mike
>> >
>> > "Pupo" wrote:
>> >
>> >> Hi
>> >> I have SQL 2000 server Sp3 on my network, i want know if is possible
>> >> obtain
>> >> major information from log file, i.e. if a user loggin to db i want
> know
>> >> the
>> >> time/date to login, operation excute etc.
>> >> Can help me please
>> >> Tia Pupo
>> >>
>> >>
>> >>
>>
>|||Hi
Those log reader tools only can report on what was changed. If someone ran a
SELECT, it is not logged as non-data monification statements are not logged
into the transaction log.
SQL Server Profiler/Trace is the only tool that will report on everything
that is going in and out the server.
Regards
Mike
"Hari Prasad" wrote:
> Hi,
> You can also use Log explorer from Lumigent. Great tool to read the
> transaction logs. Try it out from:-
> www.Lumigent.com
> Thanks
> Hari
> SQL Server MVP
> "Pupo" <123star@.libero.it> wrote in message
> news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> > Thanks i try it, in others newsgroup tell me about specific programm to
> > monitorate log as "log explorer" someone have use it before?
> > Tia
> >
> >
> > "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> > news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> >> Hi,
> >>
> >> How to Enable the Audit for Logins:-
> >> --
> >> SQL 2000 - Open enterprise manager -- Right click on server and select
> >> properties and then choose the Security tab and
> >>
> >> select Audit level "ALL" and click Ok and restart SQL server service.
> >>
> >>
> >> Operation excuted: These information can not be looged into the SQL
> >> Server
> >> error log. But you could create the trace and schedule it to
> >>
> >> run and log to a file. See the commands
> >>
> >> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> >>
> >> Thanks
> >>
> >> Hari
> >>
> >> SQL Server MVP
> >>
> >>
> >> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> >> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
> >> > Hi
> >> >
> >> > Logins/Logout can be logged into the SQL Event log, but what the user
> >> > executed, you need to use Profiler for that.
> >> >
> >> > Generally, for SOX compliance, people run Profiler to capture all the
> >> > events
> >> > and use that to report on.
> >> >
> >> > Regards
> >> > Mike
> >> >
> >> > "Pupo" wrote:
> >> >
> >> >> Hi
> >> >> I have SQL 2000 server Sp3 on my network, i want know if is possible
> >> >> obtain
> >> >> major information from log file, i.e. if a user loggin to db i want
> > know
> >> >> the
> >> >> time/date to login, operation excute etc.
> >> >> Can help me please
> >> >> Tia Pupo
> >> >>
> >> >>
> >> >>
> >>
> >>
> >
> >
>
>
I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
major information from log file, i.e. if a user loggin to db i want know the
time/date to login, operation excute etc.
Can help me please
Tia PupoHi
Logins/Logout can be logged into the SQL Event log, but what the user
executed, you need to use Profiler for that.
Generally, for SOX compliance, people run Profiler to capture all the events
and use that to report on.
Regards
Mike
"Pupo" wrote:
> Hi
> I have SQL 2000 server Sp3 on my network, i want know if is possible obtain
> major information from log file, i.e. if a user loggin to db i want know the
> time/date to login, operation excute etc.
> Can help me please
> Tia Pupo
>
>|||Hi,
How to Enable the Audit for Logins:-
--
SQL 2000 - Open enterprise manager -- Right click on server and select
properties and then choose the Security tab and
select Audit level "ALL" and click Ok and restart SQL server service.
Operation excuted: These information can not be looged into the SQL Server
error log. But you could create the trace and schedule it to
run and log to a file. See the commands
sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
Thanks
Hari
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
> Hi
> Logins/Logout can be logged into the SQL Event log, but what the user
> executed, you need to use Profiler for that.
> Generally, for SOX compliance, people run Profiler to capture all the
> events
> and use that to report on.
> Regards
> Mike
> "Pupo" wrote:
>> Hi
>> I have SQL 2000 server Sp3 on my network, i want know if is possible
>> obtain
>> major information from log file, i.e. if a user loggin to db i want know
>> the
>> time/date to login, operation excute etc.
>> Can help me please
>> Tia Pupo
>>|||Thanks i try it, in others newsgroup tell me about specific programm to
monitorate log as "log explorer" someone have use it before?
Tia
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> Hi,
> How to Enable the Audit for Logins:-
> --
> SQL 2000 - Open enterprise manager -- Right click on server and select
> properties and then choose the Security tab and
> select Audit level "ALL" and click Ok and restart SQL server service.
>
> Operation excuted: These information can not be looged into the SQL Server
> error log. But you could create the trace and schedule it to
> run and log to a file. See the commands
> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> Thanks
> Hari
> SQL Server MVP
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
> > Hi
> >
> > Logins/Logout can be logged into the SQL Event log, but what the user
> > executed, you need to use Profiler for that.
> >
> > Generally, for SOX compliance, people run Profiler to capture all the
> > events
> > and use that to report on.
> >
> > Regards
> > Mike
> >
> > "Pupo" wrote:
> >
> >> Hi
> >> I have SQL 2000 server Sp3 on my network, i want know if is possible
> >> obtain
> >> major information from log file, i.e. if a user loggin to db i want
know
> >> the
> >> time/date to login, operation excute etc.
> >> Can help me please
> >> Tia Pupo
> >>
> >>
> >>
>|||Sounds like you are asking about this product:
http://www.lumigent.com/products/le_sql.html
It works quite well.
Steve
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > How to Enable the Audit for Logins:-
> > --
> > SQL 2000 - Open enterprise manager -- Right click on server and select
> > properties and then choose the Security tab and
> >
> > select Audit level "ALL" and click Ok and restart SQL server service.
> >
> >
> > Operation excuted: These information can not be looged into the SQL
Server
> > error log. But you could create the trace and schedule it to
> >
> > run and log to a file. See the commands
> >
> > sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> >
> > Thanks
> >
> > Hari
> >
> > SQL Server MVP
> >
> >
> > "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> > news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
> > > Hi
> > >
> > > Logins/Logout can be logged into the SQL Event log, but what the user
> > > executed, you need to use Profiler for that.
> > >
> > > Generally, for SOX compliance, people run Profiler to capture all the
> > > events
> > > and use that to report on.
> > >
> > > Regards
> > > Mike
> > >
> > > "Pupo" wrote:
> > >
> > >> Hi
> > >> I have SQL 2000 server Sp3 on my network, i want know if is possible
> > >> obtain
> > >> major information from log file, i.e. if a user loggin to db i want
> know
> > >> the
> > >> time/date to login, operation excute etc.
> > >> Can help me please
> > >> Tia Pupo
> > >>
> > >>
> > >>
> >
> >
>|||Hi,
You can also use Log explorer from Lumigent. Great tool to read the
transaction logs. Try it out from:-
www.Lumigent.com
Thanks
Hari
SQL Server MVP
"Pupo" <123star@.libero.it> wrote in message
news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> Thanks i try it, in others newsgroup tell me about specific programm to
> monitorate log as "log explorer" someone have use it before?
> Tia
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
>> Hi,
>> How to Enable the Audit for Logins:-
>> --
>> SQL 2000 - Open enterprise manager -- Right click on server and select
>> properties and then choose the Security tab and
>> select Audit level "ALL" and click Ok and restart SQL server service.
>>
>> Operation excuted: These information can not be looged into the SQL
>> Server
>> error log. But you could create the trace and schedule it to
>> run and log to a file. See the commands
>> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
>> Thanks
>> Hari
>> SQL Server MVP
>>
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
>> > Hi
>> >
>> > Logins/Logout can be logged into the SQL Event log, but what the user
>> > executed, you need to use Profiler for that.
>> >
>> > Generally, for SOX compliance, people run Profiler to capture all the
>> > events
>> > and use that to report on.
>> >
>> > Regards
>> > Mike
>> >
>> > "Pupo" wrote:
>> >
>> >> Hi
>> >> I have SQL 2000 server Sp3 on my network, i want know if is possible
>> >> obtain
>> >> major information from log file, i.e. if a user loggin to db i want
> know
>> >> the
>> >> time/date to login, operation excute etc.
>> >> Can help me please
>> >> Tia Pupo
>> >>
>> >>
>> >>
>>
>|||Hi
Those log reader tools only can report on what was changed. If someone ran a
SELECT, it is not logged as non-data monification statements are not logged
into the transaction log.
SQL Server Profiler/Trace is the only tool that will report on everything
that is going in and out the server.
Regards
Mike
"Hari Prasad" wrote:
> Hi,
> You can also use Log explorer from Lumigent. Great tool to read the
> transaction logs. Try it out from:-
> www.Lumigent.com
> Thanks
> Hari
> SQL Server MVP
> "Pupo" <123star@.libero.it> wrote in message
> news:OBzC7VpPFHA.576@.TK2MSFTNGP15.phx.gbl...
> > Thanks i try it, in others newsgroup tell me about specific programm to
> > monitorate log as "log explorer" someone have use it before?
> > Tia
> >
> >
> > "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> > news:%23EWsVRpPFHA.3788@.tk2msftngp13.phx.gbl...
> >> Hi,
> >>
> >> How to Enable the Audit for Logins:-
> >> --
> >> SQL 2000 - Open enterprise manager -- Right click on server and select
> >> properties and then choose the Security tab and
> >>
> >> select Audit level "ALL" and click Ok and restart SQL server service.
> >>
> >>
> >> Operation excuted: These information can not be looged into the SQL
> >> Server
> >> error log. But you could create the trace and schedule it to
> >>
> >> run and log to a file. See the commands
> >>
> >> sp_trace_create, sp_trace_setevent, sp_trace_setstatus in books online.
> >>
> >> Thanks
> >>
> >> Hari
> >>
> >> SQL Server MVP
> >>
> >>
> >> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> >> news:E2A4F98E-5C4C-46B0-BE40-EDB530C6162E@.microsoft.com...
> >> > Hi
> >> >
> >> > Logins/Logout can be logged into the SQL Event log, but what the user
> >> > executed, you need to use Profiler for that.
> >> >
> >> > Generally, for SOX compliance, people run Profiler to capture all the
> >> > events
> >> > and use that to report on.
> >> >
> >> > Regards
> >> > Mike
> >> >
> >> > "Pupo" wrote:
> >> >
> >> >> Hi
> >> >> I have SQL 2000 server Sp3 on my network, i want know if is possible
> >> >> obtain
> >> >> major information from log file, i.e. if a user loggin to db i want
> > know
> >> >> the
> >> >> time/date to login, operation excute etc.
> >> >> Can help me please
> >> >> Tia Pupo
> >> >>
> >> >>
> >> >>
> >>
> >>
> >
> >
>
>
Subscribe to:
Posts (Atom)