not only that, but you can access sql servers that are in different states as well

i had a similar issue on a publisher and subscriber where a query execution plan was too different. toned down the maintenance.

we used to run alter index rebuild, then updatae...

get a copy of MS Access, dump your data into the Access db via linked tables and run your queries against the access db

i think you need Windows 2003 and SAN software that supports VSS

it can be used for buffer cache, but each process is limited to 4GB on a 32bit server

i'm seeing something similar, but only on servers that are configured as distributors. in my user created jobs i checked off show history or something like that on each step....

select crap from tbljunk inner join on uselessdata..tblmorejunk on stupidcolumn = dumbercolumn

i call it a sucker rally, volume has been too low

stock market has been a lot more intersting than SQL lately

this thing died down some, like they always do. next months we'll probably change passwords, but the lockdown plan is...

you can add extra drives, keep the default small by limiting growth and give unlimited growth to the ones on the other drives

you have to test

we have an old version of weblogic and testing their XA driver for that version with 64 bit SQL. there is nothing major, but there could be...

for now we just changed the password on a user account and the developer changed a few things.

problem is we have a few sql accounts with the same username/password across...

use SSIS

just make sure the db's are on the new server along with operators, etc

another day, another build

i'll try that

not a sp, but a query from a web application for a report