Viewing 15 posts - 31 through 45 (of 63 total)
DO you see any error messages in sql errorlog (not exact but something similar)
spid73 A time-out occurred while waiting for buffer latch -- type 4,...
May 11, 2009 at 3:33 pm
how about transaction repliction with immediate update
April 30, 2009 at 11:45 am
Thanks .
What i understand that by default in sql 2005 it creates a snapshot and then runs the checkdb on the snapshot db increasing the concurreny and reducing the lock...
April 30, 2009 at 11:38 am
well first the issue is with TempDB. I would suggest follow Kb937343 might be we are hiting a bug. apply SP3 and do a regression testing and if that helps...
April 30, 2009 at 3:27 am
Quick fix
===
Copy the model database(MDF and LDF) of any other instance of same build and replace the model files.
Regarding the Root cause. then we need to check the errorlogs and...
April 20, 2009 at 7:05 pm
use msdb
go
select * from sysjobs --collect all the job information
go
begin tran
'
delete from dbo.sysmaintplan_log where subplan_id =
'<>'
delete from dbo.sysmaintplan_subplans where job_id =
'<>'
delete from dbo.sysjobschedules where job_id =
'<>'
delete from...
April 10, 2009 at 3:42 pm
This dont gurantee 5GB. I tried and one was 5.4 and other was around 4.6 % . Its approximately same but it is not the exact figure
April 9, 2009 at 4:33 pm
Doing so much like creating index and rebuilding and all that stuff. But did you actually checked the execution plan of the query which is getting fired and how is...
April 8, 2009 at 10:16 am
Thanks. Sorry , I forgot to add the information.
I was able to restore the backup in SQL 2005. So, i am not sure if it is a real corruption.
I...
April 7, 2009 at 11:57 am
http://support.microsoft.com/kb/329487
--This is pre SP3 fixed
http://support.microsoft.com/kb/831950
No logshipping configured
I went through the articles. I can apply SP4 and check if it is resolved.However, as it is production, i...
April 7, 2009 at 10:42 am
I am restoring a user DB to SQL 2000 SP3/SP4
April 7, 2009 at 8:32 am
is this database upgraded from SQL 2000 to SQL 2005.
CHECKCATALOG in sql 2005 is more rigrous than sql 2000
April 3, 2009 at 11:50 am
Trace flag 818 may help to find exact reason. I can bet issue is because of I/O subsystem.
Check the I/O subsystem
Enable TF 818 to find more information if it occurs...
April 3, 2009 at 11:48 am
No Noel..
Take this scenario...
I have an instance with multiple log files and they are in the drive say F
now i moved the instance to a different drive..
I change the...
February 10, 2009 at 8:26 pm
Viewing 15 posts - 31 through 45 (of 63 total)