Debugging SQL Server 2000

I'm using SQL Server 2000 for about six months and never has a problems, but since three day ago sqlserver is freezing the server ( Win 2000 advanced server ) with no apparent reason. We're sure that is SQLServer who's causing the problem because the serv
er freezes when we are inserting records to a table.
It throws no errors... just a timeout and we have to restart the computer.
Table log is not full.
Sql Server Logs says nothing...
Is there any form to log all activities of the sql server? How can I found the cause of this problem?
Any ideas?
Thanks.
Tools you can use when this happens:
sp_who2 to check blocking and runnable processes
profiler to see what's going on
sp_lock to see what tables are being locked
perfmon to monitor resource: cpu, memory, disk I/O, etc.
"MiCiudadDevs" <MiCiudadDevs@.discussions.microsoft.com> wrote in message
news:198F91B3-E85F-456A-855D-DAE5E4D088DA@.microsoft.com...
> I'm using SQL Server 2000 for about six months and never has a problems,
but since three day ago sqlserver is freezing the server ( Win 2000 advanced
server ) with no apparent reason. We're sure that is SQLServer who's causing
the problem because the server freezes when we are inserting records to a
table.
> It throws no errors... just a timeout and we have to restart the computer.
> Table log is not full.
> Sql Server Logs says nothing...
> Is there any form to log all activities of the sql server? How can I found
the cause of this problem?
> Any ideas?
> Thanks.
|||Try using the SQL Server Profiler to monitor all the SQL statements and
writing the output to a table.
"MiCiudadDevs" <MiCiudadDevs@.discussions.microsoft.com> wrote in message
news:198F91B3-E85F-456A-855D-DAE5E4D088DA@.microsoft.com...
> I'm using SQL Server 2000 for about six months and never has a problems,
but since three day ago sqlserver is freezing the server ( Win 2000 advanced
server ) with no apparent reason. We're sure that is SQLServer who's causing
the problem because the server freezes when we are inserting records to a
table.
> It throws no errors... just a timeout and we have to restart the computer.
> Table log is not full.
> Sql Server Logs says nothing...
> Is there any form to log all activities of the sql server? How can I found
the cause of this problem?
> Any ideas?
> Thanks.

Debugging SQL Server 2000

I'm using SQL Server 2000 for about six months and never has a problems, but
since three day ago sqlserver is freezing the server ( Win 2000 advanced se
rver ) with no apparent reason. We're sure that is SQLServer who's causing t
he problem because the serv
er freezes when we are inserting records to a table.
It throws no errors... just a timeout and we have to restart the computer.
Table log is not full.
Sql Server Logs says nothing...
Is there any form to log all activities of the sql server? How can I found t
he cause of this problem?
Any ideas?
Thanks.Tools you can use when this happens:
sp_who2 to check blocking and runnable processes
profiler to see what's going on
sp_lock to see what tables are being locked
perfmon to monitor resource: cpu, memory, disk I/O, etc.
"MiCiudadDevs" <MiCiudadDevs@.discussions.microsoft.com> wrote in message
news:198F91B3-E85F-456A-855D-DAE5E4D088DA@.microsoft.com...
> I'm using SQL Server 2000 for about six months and never has a problems,
but since three day ago sqlserver is freezing the server ( Win 2000 advanced
server ) with no apparent reason. We're sure that is SQLServer who's causing
the problem because the server freezes when we are inserting records to a
table.
> It throws no errors... just a timeout and we have to restart the computer.
> Table log is not full.
> Sql Server Logs says nothing...
> Is there any form to log all activities of the sql server? How can I found
the cause of this problem?
> Any ideas?
> Thanks.|||Try using the SQL Server Profiler to monitor all the SQL statements and
writing the output to a table.
"MiCiudadDevs" <MiCiudadDevs@.discussions.microsoft.com> wrote in message
news:198F91B3-E85F-456A-855D-DAE5E4D088DA@.microsoft.com...
> I'm using SQL Server 2000 for about six months and never has a problems,
but since three day ago sqlserver is freezing the server ( Win 2000 advanced
server ) with no apparent reason. We're sure that is SQLServer who's causing
the problem because the server freezes when we are inserting records to a
table.
> It throws no errors... just a timeout and we have to restart the computer.
> Table log is not full.
> Sql Server Logs says nothing...
> Is there any form to log all activities of the sql server? How can I found
the cause of this problem?
> Any ideas?
> Thanks.

Debugging SQL

Hi All
win 2k(pro0 sql server 2k (dev ed) asp-vbscript
I'm still learning how to code in SQL... I've found the "Debug"
command in QA for debuging stored procs but I cant seem to debug other
stuff... functions, triggers etc. I cant even debug code in the QA
that I write to test before I put the final version in a store proc.
Is there anyway of debugging at least the batch sql code I write in
the QA before I put it in the store proc... any 3rd party software if
cant be done in QA? or do I have to write it and put it in a stored
proc then debug it? how do you pros do it?
thanks for any info.
AlYou can debug triggers is you execute the DML statement (Insert, Update or
Delete) that fires the trigger inside a SP - then you can debug the SP. The
same is true for a UDF - call if from a SP. VS.NET IDE has debugger as well.
--
Dejan Sarka, SQL Server MVP
FAQ from Neil & others at: http://www.sqlserverfaq.com
Please reply only to the newsgroups.
PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Harag" <harag@.softhome.net> wrote in message
news:v703mvgc4h59u8hcn0d32k8fk8p777kle0@.4ax.com...
> Hi All
> win 2k(pro0 sql server 2k (dev ed) asp-vbscript
> I'm still learning how to code in SQL... I've found the "Debug"
> command in QA for debuging stored procs but I cant seem to debug other
> stuff... functions, triggers etc. I cant even debug code in the QA
> that I write to test before I put the final version in a store proc.
> Is there anyway of debugging at least the batch sql code I write in
> the QA before I put it in the store proc... any 3rd party software if
> cant be done in QA? or do I have to write it and put it in a stored
> proc then debug it? how do you pros do it?
> thanks for any info.
> Al