I don't think that the case with SQL SERVER.

Check SQL error log and event veiwer (application log and system log) for any errors related to sql server.

You posted this on SQL 2005... Is your server 2005?

dbcc rebuild_log command retired in 2005...

dbcc rebuild_log is used to build the log file if you lost the log file and db marked suspect...

What is the reason for your db suspect..

If you can put the...

If you are not adding/deleting logins, alerts, mp, dts packages, job ect... every day then weekly should be fine other wise it should be daily...

I don't see any reason not...

Did you discuss/warn this with your manager/cto?

I know it is hard to convince managers some times...

Good luck Linda...

Write the info to a table and create a new procedure and schedule it to run every 1/5/10 minutes to send an email based on your criteria using sql mail...

you said only system dbs are there and at the same time all dbs are on SAN...

Means you server contains only system dbs not any user dbs and all of...

It is already 99% and I don't think you can improve anything else...

I don't remember it where I read but you may not get 100% even after reindexing in some...

How your query is working 2000?

It is not working either in 2000 or 2005... it is giving me the same error.

What version/Build you are on 2000?

Here is the test script...

In 2000 if you want row number then you have use identity column and a temp table...

SELECT TOP 10 identity( int) as rownumber, phone_no,model,cur_version

Some people use SQL for the name not for the DB functionality

Start SQLSAC and select remote computer and enter the virtual sql server name.

Check the following link:

http://msdn2.microsoft.com/en-us/library/ms173748.aspx

http://msdn2.microsoft.com/en-us/library/ms189117.aspx

MP is using SSIS packages so you may not get complete info as you were getting in 2000.

Most of the MP tables in 2005 cmments from BOL:

Table is included in...

Your qeustion is not clear...