Solved this - I do feel somewhat guilty but...... We'd rebuilt a node and the new nodes was at .818 and the existing at .760 it seems the handles...
Two viewpoints:- 1. Turned down by agencies/employers for selection as have no mcdba 2. Interviewed a number of mcdba's ( as an employer ) 1 had...
The "write to windows .... " box just happens to be opposite the failed option. Tick the box to write all events to the server log.
EM can often show strange results, I don't normally worry - just hit refresh and try again < grin > most likely you needed to hit F5.
If your database is making lots of autoshrink ops you will get ntfs fragmentation - back in the days of sql 6 devices had to be predefined with...
These are my notes for suspect databases, not all tested - mainly for 2k How to recover a suspect database. Top Tips 1. If the sytem dbs are ok...
Courses are very useful as they can give you an insight into how microsoft sees their products, you also get to meet similar people as yourself. I...
one possible path to follow is your log drives, we had a couple of problems where the log drive seemed to go off line ( a scssi issue ) this will...
There are a large number of jobs on all the affected servers, I don't actually see any common factor as our other cluster boxes are running...
I'm using 4 way zeon 4's ( 8 procs with HT ) and used 2 way zeon 4's previously ( 4 procs with HT ) never had any problems and got a good boost for...
We don't get any errors of any kind <grin > The problem shows as for instance:- right click on a job and run the job - nothing happens. Scheduled...
I seem to be having problems with the Agent Service running away with handles - the end result is that agent tasks stop working and the whole server...
I thank you very much for your response and assistance - I looked at the query and deduced a lack of indexes ( no clustered index 500k rows ) no nci...
yes and no .. seems that this most likely indicates poor indexing, out of date stats ... the usual things. It's nice we have all this information at...
I have a query that uses 64% for an Index Spool/Eager Spool. msdn doesn't tell me if this is a good thing or a bad thing and I can't find any info .....
Separate names with a comma.
