Why did someone do it :unsure:, if...

DBCC increases the log file size, you need to watch for it. If your table size is too big then log will grow to a substantial amount. Better switch to...

Yes Gail..you are right with that, I mean to say use Shrink DB as a emergency measure only..like when the log file grows too large after a one off ...

Server collation change calls for re-installation.Instead change DB collation as

ALTER DATABASE MyDatabase COLLATE

Watch out if you use temporary tables a lot and do joins to your databases.....

Maybe you can Purge the historical data and also Update statistics with full scan.Shrinking a DB that needs to grow is a temporal solution. As said in the above post,...

Are you running low on disk space? if so then DB shrink is good. Your DBA's are right the reason being it increases fragmentation on your tables..

Thanks!!

This looks more of a bug. What version of SQL and Service pack are you on. I would suggest to go for a higher cumulative update.

Thanks!!

No need to take DB offline...just do it on a maintenance window for the first time to note how long it takes to complete. From there you can schedule it...

I was on 3042 (default SP2 version). I have a A/P cluster. I installed from the Active node..which works very well

Mirroring is used as a High Availability technique, not risky I must say. But you cant configure it for high performance also.

Check DB Mirroring in BOL for more details.

Thanks!!

Whats the size of the largest DB of the 4000 that are installed on this instance??

I recently installed it on my server. Are there any known issues so far with SQL 2005 SP3...any comments and or views will he highly appreciated..hope there are not many...

There is no harm in Defragmenting the SAN. The advantage of defragmentation would be reducing file system overhead before any physical disk IO occurs. Also the file would be in...

shrinking operation disregards indexing..which degrades the performance. What calls for you to shrink the database.

If its only the log file that has grown too big then try thi

use UrDbName

Backup Log...

Check for Replication in BOL. But unless it is unidirectional replication (as in snapshot or transactional) you lose the ability to control the changes that you would want to go...