Viewing 15 posts - 4,966 through 4,980 (of 6,679 total)
This is generally caused by having a lower version of the client tools accessing a higher version of the database. For example, your client tools are probably at RTM...
June 22, 2009 at 8:24 pm
I find this section the most interesting:
06/09/2009 10:18:50,spid94,Unknown,***Stack Dump being sent to R:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0376.txt
06/09/2009 10:18:50,spid94,Unknown,**Dump thread - spid = 94 PSS = 0x51F2B5E0 EC = 0x51F2B5E8
06/09/2009 10:18:50,spid94,Unknown,Using...
June 22, 2009 at 8:19 pm
There is a very good article on this site about setting up Kerberos. Here are a few of my thoughts on your issue:
1) Running as sysadmin does not guarantee...
June 22, 2009 at 8:09 pm
Robb (6/22/2009)
June 22, 2009 at 2:27 pm
Glad I could help - I am happy to hear that you already have the tools, now it's just a matter of setting it up.
June 22, 2009 at 2:02 pm
Robb (6/22/2009)
Jeff-Same file for Transaction Log backup.
Init on the first run and append there after.
Robb
And there is your problem. Find out what time that file is getting backed up...
June 22, 2009 at 1:50 pm
Are you backing up to a differently named file each time? Or, are you backing up to the same file all the time?
If the same file, then you are...
June 22, 2009 at 1:33 pm
I would spend the money on Redgates SQL Compare tools. You would need the professional version to be able to automate the process daily.
What you would schedule would be...
June 22, 2009 at 1:30 pm
In a cluster, the SQL Server service is not running on the non-active node. When the failover occurs, Cluster Administrator starts SQL Server on the non-active node making it...
June 22, 2009 at 11:48 am
Using Powershell, the first step is to load the SMO libraries:
PS> [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SQLServer.SMO") | Out-Null
The next step is to setup the list of the SQL Server instances we want to access,...
June 21, 2009 at 9:05 pm
Jeff Moden (6/21/2009)
June 21, 2009 at 11:39 am
GilaMonster (6/20/2009)
Jeffrey Williams (6/20/2009)
The maintenance plan plug-in uses UPDATE STATISTICS.
So if you're using the default maint plans, updating stats after rebuilding indexes will (I think) lead to a...
June 21, 2009 at 11:31 am
The automated way of handling this is to perform regular transaction log backups. Every hour would be a good start, but you then need to follow up with the...
June 20, 2009 at 3:17 pm
The maintenance plan plug-in uses UPDATE STATISTICS. I get around this by using an Execute SQL Task and executing:
Use db1; Execute sp_updatestats @resample = 'RESAMPLE';
Use db2; Execute sp_updatestats @resample...
June 20, 2009 at 3:15 pm
GilaMonster (6/20/2009)
June 20, 2009 at 2:57 pm
Viewing 15 posts - 4,966 through 4,980 (of 6,679 total)