Database Overwritten: sp4

Showing posts with label sp4. Show all posts

Sunday, March 11, 2012

Database Maintenance Plans - Not removing Files Older than x days

I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
database on the server and have created a database maintenance plan that
backups up all the database nightly. I have also configured the maintenance
plan to delete back files older than 3 days old but this isn't currently
happening.
I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
seen this problem first. Or if anyone can confirm SP4 fixes this issue.You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
SP4 on another system to make sure your apps work correctly first, of course.
Have you checked the various logs SQL Server uses? There's a SQL Server Log,
a SQL Server Agent Log, and the Windows Application Event Log. They might
point out what is happening.
That being said, there is an extended stored procedure that Microsoft uses
to delete the files. If the Agent service doesn't have the proper rights to
the subdirectory you might find that to be the issue.
"Gary S" wrote:
> I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> database on the server and have created a database maintenance plan that
> backups up all the database nightly. I have also configured the maintenance
> plan to delete back files older than 3 days old but this isn't currently
> happening.
> I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> seen this problem first. Or if anyone can confirm SP4 fixes this issue.
>|||What is the extended store procedure that's used so that I can check it
hasn't been removed.
"Buck Woody - Microsoft SQL Server Team" wrote:
> You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
> SP4 on another system to make sure your apps work correctly first, of course.
> Have you checked the various logs SQL Server uses? There's a SQL Server Log,
> a SQL Server Agent Log, and the Windows Application Event Log. They might
> point out what is happening.
> That being said, there is an extended stored procedure that Microsoft uses
> to delete the files. If the Agent service doesn't have the proper rights to
> the subdirectory you might find that to be the issue.
> "Gary S" wrote:
> > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> > database on the server and have created a database maintenance plan that
> > backups up all the database nightly. I have also configured the maintenance
> > plan to delete back files older than 3 days old but this isn't currently
> > happening.
> >
> > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> > seen this problem first. Or if anyone can confirm SP4 fixes this issue.
> >
> >|||It's sp_delete_file - and it's undocumented, meaning unsupported for direct
use by users. Check this thread:
https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17
"Gary S" wrote:
> What is the extended store procedure that's used so that I can check it
> hasn't been removed.
> "Buck Woody - Microsoft SQL Server Team" wrote:
> > You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
> > SP4 on another system to make sure your apps work correctly first, of course.
> >
> > Have you checked the various logs SQL Server uses? There's a SQL Server Log,
> > a SQL Server Agent Log, and the Windows Application Event Log. They might
> > point out what is happening.
> >
> > That being said, there is an extended stored procedure that Microsoft uses
> > to delete the files. If the Agent service doesn't have the proper rights to
> > the subdirectory you might find that to be the issue.
> >
> > "Gary S" wrote:
> >
> > > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> > > database on the server and have created a database maintenance plan that
> > > backups up all the database nightly. I have also configured the maintenance
> > > plan to delete back files older than 3 days old but this isn't currently
> > > happening.
> > >
> > > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> > > seen this problem first. Or if anyone can confirm SP4 fixes this issue.
> > >
> > >|||Slight correction - that's XP_delete_file. Had an S in there!
"Buck Woody - Microsoft SQL Server Team" wrote:
> It's sp_delete_file - and it's undocumented, meaning unsupported for direct
> use by users. Check this thread:
> https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17
>
> "Gary S" wrote:
> > What is the extended store procedure that's used so that I can check it
> > hasn't been removed.
> >
> > "Buck Woody - Microsoft SQL Server Team" wrote:
> >
> > > You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
> > > SP4 on another system to make sure your apps work correctly first, of course.
> > >
> > > Have you checked the various logs SQL Server uses? There's a SQL Server Log,
> > > a SQL Server Agent Log, and the Windows Application Event Log. They might
> > > point out what is happening.
> > >
> > > That being said, there is an extended stored procedure that Microsoft uses
> > > to delete the files. If the Agent service doesn't have the proper rights to
> > > the subdirectory you might find that to be the issue.
> > >
> > > "Gary S" wrote:
> > >
> > > > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> > > > database on the server and have created a database maintenance plan that
> > > > backups up all the database nightly. I have also configured the maintenance
> > > > plan to delete back files older than 3 days old but this isn't currently
> > > > happening.
> > > >
> > > > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> > > > seen this problem first. Or if anyone can confirm SP4 fixes this issue.
> > > >
> > > >|||On Feb 14, 8:35 am, Gary S <G...@.discussions.microsoft.com> wrote:
> I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> database on the server and have created a database maintenance plan that
> backups up all the database nightly. I have also configured the maintenance
> plan to delete back files older than 3 days old but this isn't currently
> happening.
> I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> seen this problem first. Or if anyone can confirm SP4 fixes this issue.
There are a couple of common causes for this:
1. The maintenance plan is configured to do transaction log backups,
but one of the databases included is in Simple mode. The plan fails
when it hits this database, and never reaches the "cleanup" step.
2. One of the files to be deleted is "in use" by another process,
such as a tape backup, causing the cleanup process to fail.
Right-click on the maintenance plan itself (not the Agent job), look
at the history, you should be able to get an actual error message from
there.|||You have to be a sysadmin to run this stored proc, even in SP2 CTP. I have
been told a fix will be raised for a later service pack.
Chris
"Buck Woody - Microsoft SQL Server Team"
<BuckWoodyMicrosoftSQLServerTeam@.discussions.microsoft.com> wrote in message
news:0751636B-0F16-40EA-BAE8-8ADE57217570@.microsoft.com...
> It's sp_delete_file - and it's undocumented, meaning unsupported for
> direct
> use by users. Check this thread:
> https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17
>
> "Gary S" wrote:
>> What is the extended store procedure that's used so that I can check it
>> hasn't been removed.
>> "Buck Woody - Microsoft SQL Server Team" wrote:
>> > You'll want to apply SP4 anyway, for lots of other reasons. Test the
>> > setup of
>> > SP4 on another system to make sure your apps work correctly first, of
>> > course.
>> >
>> > Have you checked the various logs SQL Server uses? There's a SQL Server
>> > Log,
>> > a SQL Server Agent Log, and the Windows Application Event Log. They
>> > might
>> > point out what is happening.
>> >
>> > That being said, there is an extended stored procedure that Microsoft
>> > uses
>> > to delete the files. If the Agent service doesn't have the proper
>> > rights to
>> > the subdirectory you might find that to be the issue.
>> >
>> > "Gary S" wrote:
>> >
>> > > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a
>> > > number of
>> > > database on the server and have created a database maintenance plan
>> > > that
>> > > backups up all the database nightly. I have also configured the
>> > > maintenance
>> > > plan to delete back files older than 3 days old but this isn't
>> > > currently
>> > > happening.
>> > >
>> > > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone
>> > > else has
>> > > seen this problem first. Or if anyone can confirm SP4 fixes this
>> > > issue.
>> > >
>> > >|||> It's sp_delete_file - and it's undocumented, meaning unsupported for direct
> use by users.
Buck,
Above is for 2005. For 2000, the files are removed by sqlmaint.exe (which is called by xp_sqlmaint
if the plan is created by the wizard).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Buck Woody - Microsoft SQL Server Team" <BuckWoodyMicrosoftSQLServerTeam@.discussions.microsoft.com>
wrote in message news:0751636B-0F16-40EA-BAE8-8ADE57217570@.microsoft.com...
> It's sp_delete_file - and it's undocumented, meaning unsupported for direct
> use by users. Check this thread:
> https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17
>
> "Gary S" wrote:
>> What is the extended store procedure that's used so that I can check it
>> hasn't been removed.
>> "Buck Woody - Microsoft SQL Server Team" wrote:
>> > You'll want to apply SP4 anyway, for lots of other reasons. Test the setup of
>> > SP4 on another system to make sure your apps work correctly first, of course.
>> >
>> > Have you checked the various logs SQL Server uses? There's a SQL Server Log,
>> > a SQL Server Agent Log, and the Windows Application Event Log. They might
>> > point out what is happening.
>> >
>> > That being said, there is an extended stored procedure that Microsoft uses
>> > to delete the files. If the Agent service doesn't have the proper rights to
>> > the subdirectory you might find that to be the issue.
>> >
>> > "Gary S" wrote:
>> >
>> > > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
>> > > database on the server and have created a database maintenance plan that
>> > > backups up all the database nightly. I have also configured the maintenance
>> > > plan to delete back files older than 3 days old but this isn't currently
>> > > happening.
>> > >
>> > > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
>> > > seen this problem first. Or if anyone can confirm SP4 fixes this issue.
>> > >
>> > >|||Thanks Tracey a number of the database were set to Simple Recovery. I'm not a
big fan of database mainatenance plans (perfer setting up the jobs
individual) so as I'm not 100% certain why the databases are set to simple
I'll create seperate backup jobs.
"Tracy McKibben" wrote:
> On Feb 14, 8:35 am, Gary S <G...@.discussions.microsoft.com> wrote:
> > I have a Windows 2000 SP4 Cluster running MS SQL 2000 SP3, I have a number of
> > database on the server and have created a database maintenance plan that
> > backups up all the database nightly. I have also configured the maintenance
> > plan to delete back files older than 3 days old but this isn't currently
> > happening.
> >
> > I haven't applied SP4 to SQL 2000 yet as I wanted to know if anyone else has
> > seen this problem first. Or if anyone can confirm SP4 fixes this issue.
> There are a couple of common causes for this:
> 1. The maintenance plan is configured to do transaction log backups,
> but one of the databases included is in Simple mode. The plan fails
> when it hits this database, and never reaches the "cleanup" step.
> 2. One of the files to be deleted is "in use" by another process,
> such as a tape backup, causing the cleanup process to fail.
> Right-click on the maintenance plan itself (not the Agent job), look
> at the history, you should be able to get an actual error message from
> there.
>|||On Feb 15, 5:13 am, Gary S <G...@.discussions.microsoft.com> wrote:
> Thanks Tracey a number of the database were set to Simple Recovery. I'm not a
> big fan of database mainatenance plans (perfer setting up the jobs
> individual) so as I'm not 100% certain why the databases are set to simple
> I'll create seperate backup jobs.
>
Here's a script of mine that might help you out:
http://realsqlguy.blogspot.com/2007/02/automating-database-backups.html

Database Maintenance Plans - Not removing Files Older than x days

Thursday, March 8, 2012

database maintenance plan

i currently am using: sharepoint portal 2003 / windows sharepoint
services with sp2 and sql 2000 with sp4.
i'm trying to develop a database maintenance plan in sql 2000. so far,
to get past the
QUOTED_IDENTIFIER, i've added -SupportComputedColumn to the T-SQL code
in the steps, but since sharepoint actively keeps a connection to the
database, i'm unable to backup the transaction logs.
i tried adding something like this:
use master
go
alter database db1_prod set single_user with rollback immediate
go
...and it didn't work. anyone have a better idea?
thanks!> but since sharepoint actively keeps a connection to the
> database, i'm unable to backup the transaction logs.
Backup log is perfectly possible while users are connected to the database. My guess is that your
integrity check has the "attempt to repair minor problems" checked. This is a bad option in the
first place. I suggest you remove that option.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<eric.olson@.gmail.com> wrote in message
news:1164121998.074547.209600@.f16g2000cwb.googlegroups.com...
>i currently am using: sharepoint portal 2003 / windows sharepoint
> services with sp2 and sql 2000 with sp4.
> i'm trying to develop a database maintenance plan in sql 2000. so far,
> to get past the
> QUOTED_IDENTIFIER, i've added -SupportComputedColumn to the T-SQL code
> in the steps, but since sharepoint actively keeps a connection to the
> database, i'm unable to backup the transaction logs.
> i tried adding something like this:
> use master
> go
> alter database db1_prod set single_user with rollback immediate
> go
> ...and it didn't work. anyone have a better idea?
> thanks!
>|||Regarding the statement:
"but since sharepoint actively keeps a connection to the
database, i'm unable to backup the transaction logs."
You can do database and log backups while the database is in use. You
don't need to drop any connections to perform the backup.
-Sue
On 21 Nov 2006 07:13:18 -0800, eric.olson@.gmail.com wrote:
>i currently am using: sharepoint portal 2003 / windows sharepoint
>services with sp2 and sql 2000 with sp4.
>i'm trying to develop a database maintenance plan in sql 2000. so far,
>to get past the
>QUOTED_IDENTIFIER, i've added -SupportComputedColumn to the T-SQL code
>in the steps, but since sharepoint actively keeps a connection to the
>database, i'm unable to backup the transaction logs.
>i tried adding something like this:
>use master
>go
>alter database db1_prod set single_user with rollback immediate
>go
>...and it didn't work. anyone have a better idea?
>thanks!|||where i'm at now:
Backup cannot be performed on database 'master'. The sub task is
ignored.
Backup cannot be performed on database 'msdb'. The sub task is ignored.
Sue Hoegemeier wrote:
> Regarding the statement:
> "but since sharepoint actively keeps a connection to the
> database, i'm unable to backup the transaction logs."
> You can do database and log backups while the database is in use. You
> don't need to drop any connections to perform the backup.
> -Sue
> On 21 Nov 2006 07:13:18 -0800, eric.olson@.gmail.com wrote:
> >i currently am using: sharepoint portal 2003 / windows sharepoint
> >services with sp2 and sql 2000 with sp4.
> >
> >i'm trying to develop a database maintenance plan in sql 2000. so far,
> >to get past the
> >QUOTED_IDENTIFIER, i've added -SupportComputedColumn to the T-SQL code
> >in the steps, but since sharepoint actively keeps a connection to the
> >database, i'm unable to backup the transaction logs.
> >
> >i tried adding something like this:
> >
> >use master
> >go
> >alter database db1_prod set single_user with rollback immediate
> >go
> >
> >...and it didn't work. anyone have a better idea?
> >
> >thanks!|||eric.olson@.gmail.com wrote:
> where i'm at now:
> Backup cannot be performed on database 'master'. The sub task is
> ignored.
> Backup cannot be performed on database 'msdb'. The sub task is ignored.
That means you're attempting to do a transaction log backup on those
databases, and they're in Simple recovery mode. You can't backup the
t-log on a Simple mode database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||i took off the 'attempt to repair minor problems' but still get errors
with the master and msdb databases backup. perhaps i need to make a
separate database maintenance plan for those two, and only have them
backup and not touch the transaction logs?
Tibor Karaszi wrote:
> > but since sharepoint actively keeps a connection to the
> > database, i'm unable to backup the transaction logs.
> Backup log is perfectly possible while users are connected to the database. My guess is that your
> integrity check has the "attempt to repair minor problems" checked. This is a bad option in the
> first place. I suggest you remove that option.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> <eric.olson@.gmail.com> wrote in message
> news:1164121998.074547.209600@.f16g2000cwb.googlegroups.com...
> >i currently am using: sharepoint portal 2003 / windows sharepoint
> > services with sp2 and sql 2000 with sp4.
> >
> > i'm trying to develop a database maintenance plan in sql 2000. so far,
> > to get past the
> > QUOTED_IDENTIFIER, i've added -SupportComputedColumn to the T-SQL code
> > in the steps, but since sharepoint actively keeps a connection to the
> > database, i'm unable to backup the transaction logs.
> >
> > i tried adding something like this:
> >
> > use master
> > go
> > alter database db1_prod set single_user with rollback immediate
> > go
> >
> > ...and it didn't work. anyone have a better idea?
> >
> > thanks!
> >|||right... but a microsoft article also said not to put master or msdb
in full mode.
should i put it in full recovery mode?
Tracy McKibben wrote:
> eric.olson@.gmail.com wrote:
> > where i'm at now:
> >
> > Backup cannot be performed on database 'master'. The sub task is
> > ignored.
> > Backup cannot be performed on database 'msdb'. The sub task is ignored.
> That means you're attempting to do a transaction log backup on those
> databases, and they're in Simple recovery mode. You can't backup the
> t-log on a Simple mode database.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||eric.olson@.gmail.com wrote:
> right... but a microsoft article also said not to put master or msdb
> in full mode.
> should i put it in full recovery mode?
>
No, just don't include those databases in the transaction log backup
job. Create two plans - one for system DB's, one for user DB's.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||that's exactly what i ended up doing :).
- plan1 - backup user databases w/transaction logs, database
optimization, and error checking
- plan2 - backup system databases and check for errors
thanks.
Tracy McKibben wrote:
> eric.olson@.gmail.com wrote:
> > right... but a microsoft article also said not to put master or msdb
> > in full mode.
> >
> > should i put it in full recovery mode?
> >
> No, just don't include those databases in the transaction log backup
> job. Create two plans - one for system DB's, one for user DB's.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Wednesday, March 7, 2012

database maintenance plan

i currently am using: sharepoint portal 2003 / windows sharepoint
services with sp2 and sql 2000 with sp4.
i'm trying to develop a database maintenance plan in sql 2000. so far,
to get past the
QUOTED_IDENTIFIER, i've added -SupportComputedColumn to the T-SQL code
in the steps, but since sharepoint actively keeps a connection to the
database, i'm unable to backup the transaction logs.
i tried adding something like this:
use master
go
alter database db1_prod set single_user with rollback immediate
go
...and it didn't work. anyone have a better idea?
thanks!> but since sharepoint actively keeps a connection to the
> database, i'm unable to backup the transaction logs.
Backup log is perfectly possible while users are connected to the database.
My guess is that your
integrity check has the "attempt to repair minor problems" checked. This is
a bad option in the
first place. I suggest you remove that option.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<eric.olson@.gmail.com> wrote in message
news:1164121998.074547.209600@.f16g2000cwb.googlegroups.com...
>i currently am using: sharepoint portal 2003 / windows sharepoint
> services with sp2 and sql 2000 with sp4.
> i'm trying to develop a database maintenance plan in sql 2000. so far,
> to get past the
> QUOTED_IDENTIFIER, i've added -SupportComputedColumn to the T-SQL code
> in the steps, but since sharepoint actively keeps a connection to the
> database, i'm unable to backup the transaction logs.
> i tried adding something like this:
> use master
> go
> alter database db1_prod set single_user with rollback immediate
> go
> ...and it didn't work. anyone have a better idea?
> thanks!
>|||Regarding the statement:
"but since sharepoint actively keeps a connection to the
database, i'm unable to backup the transaction logs."
You can do database and log backups while the database is in use. You
don't need to drop any connections to perform the backup.
-Sue
On 21 Nov 2006 07:13:18 -0800, eric.olson@.gmail.com wrote:

>i currently am using: sharepoint portal 2003 / windows sharepoint
>services with sp2 and sql 2000 with sp4.
>i'm trying to develop a database maintenance plan in sql 2000. so far,
>to get past the
>QUOTED_IDENTIFIER, i've added -SupportComputedColumn to the T-SQL code
>in the steps, but since sharepoint actively keeps a connection to the
>database, i'm unable to backup the transaction logs.
>i tried adding something like this:
>use master
>go
>alter database db1_prod set single_user with rollback immediate
>go
>...and it didn't work. anyone have a better idea?
>thanks!|||where i'm at now:
Backup cannot be performed on database 'master'. The sub task is
ignored.
Backup cannot be performed on database 'msdb'. The sub task is ignored.
Sue Hoegemeier wrote:[vbcol=seagreen]
> Regarding the statement:
> "but since sharepoint actively keeps a connection to the
> database, i'm unable to backup the transaction logs."
> You can do database and log backups while the database is in use. You
> don't need to drop any connections to perform the backup.
> -Sue
> On 21 Nov 2006 07:13:18 -0800, eric.olson@.gmail.com wrote:
>|||eric.olson@.gmail.com wrote:
> where i'm at now:
> Backup cannot be performed on database 'master'. The sub task is
> ignored.
> Backup cannot be performed on database 'msdb'. The sub task is ignored.
That means you're attempting to do a transaction log backup on those
databases, and they're in Simple recovery mode. You can't backup the
t-log on a Simple mode database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||i took off the 'attempt to repair minor problems' but still get errors
with the master and msdb databases backup. perhaps i need to make a
separate database maintenance plan for those two, and only have them
backup and not touch the transaction logs?
Tibor Karaszi wrote:[vbcol=seagreen]
> Backup log is perfectly possible while users are connected to the database
. My guess is that your
> integrity check has the "attempt to repair minor problems" checked. This i
s a bad option in the
> first place. I suggest you remove that option.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> <eric.olson@.gmail.com> wrote in message
> news:1164121998.074547.209600@.f16g2000cwb.googlegroups.com...|||right... but a microsoft article also said not to put master or msdb
in full mode.
should i put it in full recovery mode?
Tracy McKibben wrote:
> eric.olson@.gmail.com wrote:
> That means you're attempting to do a transaction log backup on those
> databases, and they're in Simple recovery mode. You can't backup the
> t-log on a Simple mode database.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||eric.olson@.gmail.com wrote:
> right... but a microsoft article also said not to put master or msdb
> in full mode.
> should i put it in full recovery mode?
>
No, just don't include those databases in the transaction log backup
job. Create two plans - one for system DB's, one for user DB's.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||that's exactly what i ended up doing

.
- plan1 - backup user databases w/transaction logs, database
optimization, and error checking
- plan2 - backup system databases and check for errors
thanks.
Tracy McKibben wrote:
> eric.olson@.gmail.com wrote:
> No, just don't include those databases in the transaction log backup
> job. Create two plans - one for system DB's, one for user DB's.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Friday, February 17, 2012

Database lock makes all Clients hold

We are using SQL2000 with SP3, Windows 2000 Svr Std with SP4
Sometimes, we found all clients had no response. Later, we found that the
all clients are waiting response from sql server.
Then in querry analyzer, we use this script:
select * FROM master..sysprocesses where status='sleeping' AND
waittype=0x000 AND open_tran > 0
and then we found out one computer is locking and after request that
computer logout the program, then, all clients can run again.
However, I have no idea why this case happen and I am still searching what's
the meaning the about select statement.
Can anyone help me?
IvanTalk to the person who wrote that program, as you have a bug in the application because it doesn't
and the transaction properly.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Ivan Kan" <ivankan@.no-ip.com> wrote in message news:uJg1Qb3lDHA.1740@.TK2MSFTNGP12.phx.gbl...
> We are using SQL2000 with SP3, Windows 2000 Svr Std with SP4
> Sometimes, we found all clients had no response. Later, we found that the
> all clients are waiting response from sql server.
> Then in querry analyzer, we use this script:
> select * FROM master..sysprocesses where status='sleeping' AND
> waittype=0x000 AND open_tran > 0
> and then we found out one computer is locking and after request that
> computer logout the program, then, all clients can run again.
> However, I have no idea why this case happen and I am still searching what's
> the meaning the about select statement.
> Can anyone help me?
> Ivan
>
>

Sunday, March 11, 2012

Database Maintenance Plans - Not removing Files Older than x days

Database Maintenance Plans - Not removing Files Older than x days

Database Maintenance Plans - Not removing Files Older than x days

Thursday, March 8, 2012

database maintenance plan

database maintenance plan

Wednesday, March 7, 2012

database maintenance plan

Friday, February 17, 2012

Database lock makes all Clients hold

Database Overwritten

Blog Archive

About Me