Viewing 15 posts - 301 through 315 (of 433 total)
Why do you want run two jobs and take the headache. You can try for
Log shipping, Replication or SQL Server cluster for the above issue.
For the issue you...
August 6, 2007 at 4:29 am
1. Did you try to fix it with DBCC CHECKDB with REPAIR_REBUILD option. Please read the recommendation to run a dbcc checkdb from BOL.
2. If this does not solve only one...
August 6, 2007 at 4:19 am
Wanted to know if AUTOGROW option is enabled ??
check this KB http://support.microsoft.com/kb/317375/en-us
Minaz
July 30, 2007 at 3:10 am
Check if any trigger is getting fired. !!
July 27, 2007 at 7:38 am
I am not sure if the Replication is causing the issue. You should have good backup plan. That will solve the issue.
Please follow these links for more info:
http://support.microsoft.com/kb/272318/en-us
July 27, 2007 at 6:17 am
As SQLBill, try to recycle the log.
What is the total server memory ? What is the max / min SQL server memory?
is there /3GB is enabled in the Boot.ini ?
July 27, 2007 at 6:12 am
You need to do a fresh installation and rebuild the cluster.
Minaz
July 27, 2007 at 1:37 am
What is memory configuration of the SQL Server. ?
1. Check if there is fragmentaion of the virtual memory then defrag it.
2. Check the output of the DBCC MEMORYSTATUS shown where...
July 27, 2007 at 1:24 am
C:\WINDOWS\Minidump\Mini070307-05.dmp. did you checked this dump file?
Minaz
July 3, 2007 at 6:05 am
As you have mentioned you are in RTM version, I would suggest it will be better if you apply SP2.
Minaz
June 28, 2007 at 4:34 am
Thanks Sugesh I learned about the SP.
Apart from this there is a good KB :
http://support.microsoft.com/kb/314546/en-us
June 28, 2007 at 3:46 am
Event ID 824 is similar to the 823 error message which is related to problem in the I/O subsystem, such as a failing disk drive, disk firmware problems, faulty device...
June 27, 2007 at 12:25 am
June 27, 2007 at 12:16 am
Michael has explained well about blocking and I have found some good KB which will also help you to understand blocking and how to troubleshoot it.
http://support.microsoft.com/kb/224453/en-us
Minaz
June 26, 2007 at 5:48 am
Hey this error itself says that network address is the problem.
1. Did you check the SQL server is listening on 1433 port.
2. Enable the TCP/IP protocol -> Client Configuration dialog...
June 26, 2007 at 5:39 am
Viewing 15 posts - 301 through 315 (of 433 total)