Viewing 15 posts - 1 through 15 (of 41 total)
November 4, 2017 at 11:23 am
Hi Steve, You may get more feedback on this than you know what to do with. There are a lot of small shops out there like the one I...
October 31, 2017 at 8:41 am
I have seen many good and thoughtful comments on here about Mickey's article.
In general what Mickey states is mostly counter to my experiences but like so many things in the...
June 2, 2015 at 12:07 pm
I have seen some strange things with collations too.
Unfortunately, I am running both the package and the sproc against the same sql server database. So,...
October 31, 2008 at 2:38 pm
Interesting idea, using an installer as a script engine to back up your databases.
Why not just use the job engine that is built in to the Sql Server?
March 6, 2006 at 1:42 pm
Performing a full database backup on a log shipping primary will break the transaction log backup chain. This will prevent you from restoring more transaction logs to the...
March 6, 2006 at 1:40 pm
No. The database structures are different. You can not restore a Sql 2005 database on Sql 2000.
If you have additional questions about this please reply to me. Unfortunately,...
March 6, 2006 at 1:17 pm
The 17883 errors are very simply Sql Server's way of telling you that some thread that was executing did not release the cpu for more than 60 seconds....
March 6, 2006 at 1:04 pm
The way to find out why your tempDB is growing is to use the profiler to create a trace you can use to monitor it.
The tempDB is used...
March 6, 2006 at 12:51 pm
I have a list of articles that I send to customers that are moving databases or going through a disaster recovery. It covers a lot of ground, but seems...
March 6, 2006 at 12:00 pm
Another reason to move the master lookup table into seperate lookup tables is that the master does not scale well. You are performing a clustered index scan. A clustered index...
May 24, 2005 at 9:47 am
You can also query the msdb directly. Backup information is stored in 4 tables here. The following query will pull most of the physical information out of them for a...
May 24, 2005 at 9:33 am
When you restore a database the sprocs are indeed recompiled the next time they are run. This is usually very fast, however very complex sprocs can take up a minute or so...
May 24, 2005 at 9:02 am
The error means that somehow your backups got out of sequence. To figure out what happened you can look at the header information on your backups to see...
May 24, 2005 at 8:58 am
For the scenario you have given this mostly to be expected.
17883 errors are reporting that a thread executing in the Sql process space did not release the CPU...
May 24, 2005 at 8:54 am