Viewing 6 posts - 1 through 6 (of 6 total)
You should run a DBCC CHECKDB as soon as possible. SQL Server is often times able to recover using one of the repair parameters (REPAIR_ALLOW_DATA_LOSS, REPAIR_FAST, REPAIR_REBUILD) for CHECKDB. The results of DBCC...
June 25, 2004 at 8:54 am
You can also right-click on the server in EM and go to properties. Under the "General" tab there is a checkbox for "Autostart SQL Server Agent".
June 25, 2004 at 8:40 am
2 things to try:
1 - You can run a profiler trace while you perform this command. This should allow you to see the SQL or stored procedure that is causing...
June 25, 2004 at 8:34 am
To rule out any SQL Server issues, you may want to upgrade to the latest service pack (SP3a). Also, you may want to try and close and re-open the access...
June 25, 2004 at 8:27 am
Just a few thoughts -
Use textimage_on for your table(s) containing the image columns holding the scanned documents in order to specify that the image data go on a separate file...
September 1, 2003 at 9:23 pm
You may want to stay away from RAID 5 for your transaction logs. You want fast writes for logs and RAID 5 weakness is writing (parity writes). RAID...
August 6, 2003 at 2:42 pm
Viewing 6 posts - 1 through 6 (of 6 total)