Viewing 12 posts - 1 through 12 (of 12 total)
Some years ago I took a sample of the standard MCDBA (or whatever it was called) test. I quit in disgust when it asked "How many tables can a SQL...
September 17, 2013 at 5:48 pm
Hey PCD that's a cool tip, thanks. 🙂
February 4, 2011 at 1:20 pm
Yup, a useful tip. As an aside, I'm bummed they discontinued rebuildm.exe. I only used it once, but it worked fine. Nobody mentioned, but (I believe since SQL 2005), you...
February 3, 2011 at 4:40 pm
Well everybody, I'm pleased my comment about starting a db maintenance job with DBCC Checkdb inspired such discussion. Just to add some clarification... I have all of my sql agent...
January 27, 2011 at 1:14 pm
Nice, Gethyn. But i like to run DBCC Checkdb as first step... If checkdb fails, the job quits and you don't end up backing up a corrupt database.
January 26, 2011 at 1:00 pm
Hi Rudy & Everyone,
Nice solution Rudy. But just to throw an angle, I have resisted taking this approach for some time. I have my reasons:
I have about 30 servers/instances. A...
January 15, 2009 at 5:17 pm
I've been using a job failure email notification method for some years now on SQL 2000 with the following differences:
1) I don't use a monitor server to check the other...
February 5, 2008 at 12:02 pm
In solving performance problems, I always go look at the code in the query or stored proc. I haven't found one yet where the cause wasn't just a poorly written...
December 4, 2007 at 4:46 pm
I've been using this one for quite some time. I like it because you can use it for combination keys (i.e. where the primary key is more than one column)....
June 4, 2004 at 6:11 pm
I always just fetch into temp tables.
August 6, 2003 at 6:40 pm
The proper tool for any job is that tool which was originally designed specifically for that job. For 2-tier client-server (which it sounds like you want), VB is NOT the...
May 31, 2002 at 6:09 pm
Viewing 12 posts - 1 through 12 (of 12 total)