Viewing 15 posts - 91 through 105 (of 468 total)
NJ-DBA (5/16/2012)
declare @job_id varchar(100)
select @job_id =job_id from msdb.dbo.sysjobs where name='Error Sev 17 or Higher Alert'
/******...
May 16, 2012 at 11:04 am
NJ-DBA (5/8/2012)
Steve Jones - SSC Editor (5/8/2012)
May 8, 2012 at 5:56 pm
Steve Jones - SSC Editor (5/8/2012)
May 8, 2012 at 2:23 pm
in the interest of full disclosure heres how it all went down:
Friday: change to simple mode, then back to full. Kicked off full litespeed backups. Litespeed transaction log...
May 8, 2012 at 2:19 pm
Using litespeed, but the problem which caused us to disable the tlog backups, was litespeed related, so when we picked it up, we went with a native backup of the...
May 8, 2012 at 2:15 pm
Probably not, but the example does help me understand how this could happen. Possibly several smaller tables truncated repeatedly, though I would be surprised if it amounted to 100GB worth....
May 8, 2012 at 1:50 pm
Well, i hopefully you can explain why the best practice doesnt make sense to your clients, because so far all i've heard in this case is "microsoft isnt always right"....
April 24, 2012 at 4:24 pm
Right- yeah, I dont need it to come from Microsoft, I just need it to be backed up some supporting data or documentation to understand why.
All I meant is that...
April 24, 2012 at 2:05 pm
I did see that, but "To improve query plans and query performance, we recommend that you update statistics on all databases following upgrade from SQL Server 2000" is not the...
April 24, 2012 at 11:53 am
realyl need to find something from MS saying to do this... cant say "some well respected posters on SQLServerCentral said so"... I mean, that's good enough for me, but...
April 24, 2012 at 11:41 am
REally- I did not know about that. Is it documented somewhere in BOL that it's mandatory to do an update stats wth fullscan after upgrading to 2008?
April 24, 2012 at 10:07 am
The execution plans were the same (which is what had me scratching my head)...
Looks like this was related to a difference in the Provider Options. "Allow inprocess" was...
April 23, 2012 at 2:03 pm
This turned out to be an issue with setup running on systems with > 32 processors. Described here: http://support.microsoft.com/kb/2251397
Resolutino was to kill setup, remove nodes, and...
April 11, 2012 at 12:17 pm
Well, have you identified what is using up so many locks? start with:
SELECT request_session_id, COUNT (*) num_locks
FROM sys.dm_tran_locks
GROUP BY request_session_id
ORDER BY count (*) DESC
April 4, 2012 at 12:32 pm
Viewing 15 posts - 91 through 105 (of 468 total)