Comments on: SQL SERVER – What the Business Says Is Not What the Business Wants

By: Lexz

Lexz — Mon, 14 Mar 2011 10:49:27 +0000

In my humble opinion, the expert, as a consultant, should be able to translate technical consequences into business consequences. Explaining what his decision means in technical terms, will never ring a bell for someone that doesn’t understand the technique.

By: SQL SERVER – Shrinking Database is Bad – Increases Fragmentation – Reduces Performance Journey to SQL Authority with Pinal Dave

Wed, 19 Jan 2011 01:32:01 +0000

[...] SQL SERVER – What the Business Says Is Not What the Business Wants [...]

By: Robert Pearl

Robert Pearl — Tue, 14 Dec 2010 18:20:51 +0000

As Pinal said, SHRINK DATABASE is not a best practice. In cases that you encounter no other option, for example, to reclaim space, it would be better to use DBCC SHRINKFILE, and specify the corresponding data or log file. I’d also use the option WITH TRUNCATE ONLY to minimize the time it would take to actually move around the data pages during this operation. It should also be done during non-peak time. Even so, SHRINKFILE on a continuous basis, also not a great option. If the issue pertains to the log file, and your not backing up the tlog regularly, better to keep it in SIMPLE recovery mode (truncate log on checkpoint), to maintain the size of the log. HTH – RP

By: Ramdas

Ramdas — Tue, 14 Dec 2010 15:06:29 +0000

A very good article. When one hires a skilled person for the job, the firm/business need to value his opinion based on understanding of the business and also share best practices in the industry.

By: aasim abdullah

aasim abdullah — Tue, 14 Dec 2010 10:57:58 +0000

Thanks for the article. Please also elaborate major benefits of SHRINKDATABASE. And specially the situations when we have no other option other then SHRINKDATABASE .

By: weicco

weicco — Tue, 14 Dec 2010 05:59:34 +0000

This is something that bugs me a lot. Or has bugged me, now I’m in a firm where they (bosses and co-workers) appreciate talent but in my previous job things were a lot different.

I’m a DBA and I’m a programmer, designer, whatever. I have over 10 years experience on the field. One might consider me as an expert on Sql Server, T/SQL and C#/.NET.

Now, why on every time when I say “No, you can’t do that becuase it will cause this” someone, who is most likely not even a DBA or programmer but someone who has “credibility” in the firm, comes and says “But we have always done it like this and this is how we keep doing it”? If one hires an expert why doesn’t one respect expert’s opinions?

If I hire a contractor to do my house wiring I don’t go and tell him how he/she should do his/her job. I know nothing about wiring so who am I to instruct an expert.

Of course I make mistakes from time to time and so does electricians make mistakes but I think our mistakes are a lot smaller ones :)