Viewing 7 posts - 1 through 7 (of 7 total)
You're saying "you may break some of your current stored procedures, as SQL 2005 is stricter about certain things,". Can you give some examples of what breaks?
January 17, 2007 at 6:40 am
Data integrity is my main reason for individual tables. We have a database that started with one large table and are gradually moving off of it. I've had many production...
October 27, 2005 at 7:35 am
I doubt that I can add anything meaningful or cite any better references for why a single lookup table isn't a good idea. I inherited a database that has a...
September 28, 2005 at 7:20 am
We use them only rarely when pushed into a corner. They have all the downsides that you've described with little, if any (in my way of thinking) offsetting benefits. If you...
September 28, 2005 at 6:52 am
Microsoft SQL Server 2000 Performance Optimization and Tuning Handbook by Ken England, Digital Press, ISBN1-55558-241-9. Has chapters on storage, indexing, the optimizer, locking, monitoring.
September 20, 2005 at 7:06 am
Continually ranked as one of the best third party SQL Server tools and priced right starting at about $200 - http://www.red-gate.com/sql/summary.htm . I use it all the time and swear by it...
May 12, 2005 at 6:26 am
We have a rule that we don't embed business logic in triggers, nor do we use them to do something (such as enforce RI) that can be done with a...
April 26, 2005 at 6:58 am
Viewing 7 posts - 1 through 7 (of 7 total)