Hi, other more experienced DBA's may advise otherwise, but my two pence worth. Try DBCC CHECKDB ('database', REPAIR_REBUILD).

Lookup the options available with DBCC CHECKDB. But I do believe generally...

I believe it will only increase the size of the sysjobhistory table in the msdb database. Rgds Derek

Hi, I'm afraid I can not see the jpeg's attached. Can you cut and past the error text into this mail thread. I love replication and the more issue I...

What error message is the Distribution Agent returning. Look at the Error Details and Agent History under Distribution Agents under Replication Monitor or else look at the actual job history...

A Guide to SQL Server 2000 Transactional & Snapshot Replication by Hillary Cotter is excellent. We have multiple replication streams running with a Central Distributor. Found this book excellent when...

Hi, probably not much use to you, but I believe once you get Torn Page Detected, you have no option but to go back to a reliable database backup. You...

Hi Timber, my approach would be install SQL Server on your new drive. Before you attach your user databases using sp_attach_db, you should consider also 'restoring' your msdb database. This...

Hi, Can you see in the SQL Server logs if a Checkpoint is being issued. Also is the transaction log being truncated at regular intervals ? In SQL Server 7...

Hope I don't sound too abrupt, but I think your IT manager sounds very infexible ! Just take a look at the CPU on the box and that will tell...

Hi, in our company two of us are Database Administrators and we have two System ( O/S, Network, Hardware ) administrators. As the lads above have clarified they are separate...

What might also be useful is SELECT SERVERPROPERTY('ProductVersion') ( Output results to text as opposed to grid in Query Analyser ). Hope this is of use. Rgds Derek

Hi, I hope to answer your question. First keep it simple. Create a publication for each database you wish to publish. Keep it simple and use the existing distribution db....

Michelle, David, Like yourselves we use events to trigger alerts etc, ie log file > 90%. However we are also evaluating SQL Sentry and Spotlight. By the way we use SQLLitespeed...

Derek here again. Having read the good input from all so far, I would now tend to take an old fashioned approach. You say select count(*) uses 100% cpu. Well...

Hi, as previous reply, we use aba_lockinfo very successfully. 

http://www.sommarskog.se/sqlutil/aba_lockinfo.html

 Rgds

Derek