Viewing 15 posts - 1 through 15 (of 2,386 total)
Try to run dbcc checktable to 'dtproperties' table in the database you received the error message to see what will you get.
August 18, 2005 at 2:38 pm
That is because you are runing the standard edition.
August 18, 2005 at 2:35 pm
Can you send back the result of following commands? Please also post your insert statement.
use tempdb
go
sp_helpfile
go
dbcc sqlperf(logspace)
You don't have to backup the tempdb at all.
August 18, 2005 at 2:30 pm
Microsoft has a tool to handle such request, Search Microsoft SQL Server website.
August 8, 2005 at 11:31 pm
Also try to update tables/indexes statistics to see whether SQL Server runs the SP using multiple processors.
I would try to find out which part of SP running slow and compare...
May 27, 2005 at 9:53 am
Can you please the link to your script. Thanks.
May 25, 2005 at 10:08 am
Are SQL Server 2000 running as named instances?
May 25, 2005 at 9:27 am
Try
dbcc rebuild_log ('Training', 'c:\Training_Log.ldf')
May 19, 2005 at 6:34 am
I think you are in right direction to look into the SP.
Adjust number of CPUs for paralleism could affect some of queries, You need to monitor them clolsely. But in...
May 19, 2005 at 6:22 am
Are you saying you were asked to downgrade SQL Server 2000 database into SQL Server 7.0? Curious why if it is?
You can't restore SQL Serevr 2000 database into SQL Server 7.0!...
May 19, 2005 at 6:16 am
Sounds like blocking, run sp_who2 to see when you notice slow performance.
May 19, 2005 at 6:11 am
Backup your original database and restore it into destination server without recovery, then continue the log shipping.
May 19, 2005 at 6:10 am
You can't. Call your DBA or reset it if you have the permissions.
May 19, 2005 at 6:06 am
What exactly did you look for?
In term of restarting servers, Don't restart both servers at same time, Always wait until restarted server is online before restarting another one.
May 19, 2005 at 6:05 am
Viewing 15 posts - 1 through 15 (of 2,386 total)