and here I found one of the good article...

http://www.mssqltips.com/tip.asp?tip=2097

you will be getting this error as long your agents are running.

Go in activity monitor and kill those connection.

then right click on replication on SSMS and select disable...

have you checked by putting proper counter in perfmon(performance monitor).

You can get these details there as well.

If you interested in tool, then I use quest PA/Spotlight and they...

instead of shrinking your database regularly, you must redefine your full and log backup schedule.

You will definately see the difference.

if it still growing, then you need to find which...

if the values in tables stored in similar way in both the server then its definately some setting which is changing he view.

Which sql version you using??

to convert datetime into text, use

convert(char(8),getdate(),112)

this is just a hint which you can further explore and use it in your code.

and can you please check in both server, query output option is selected to same format.

Either to grid or to text

what are your select query and output format

if you doing the logfile shrink then you can get additional information by :-

dbbc loginfo(dbname).

Status 2 means in use and 0 means free to reuse or available for shrink.

Agree with Steve, you should let the backup on specific server. But in addition, you can schedule another job which will copy the backup from all server to that single...

have you googled about shrinkfile/shrinkdatabase and not able to find your answer there?

I think in forum we genrally post the live example error not the information or knowledge upgrade...

check BOL

from performance perspective, it should be clustered index with appropriate fill factor.

Also make sure the index is being updated regularly for threshold limit like :-

if fregmentation is <30 then reorganise...

but if its secured connection which is connecting to database then i dont think reading matters that much. They have no permisssion to modify it.

Correct me if I am wrong.

then in that case I think we need to setup the auditing on every connection getting connected to database.