super easy but completely ran on auto pilot with a list of names by taking out duplicates.

copy everything except the x64 and ia64 folders and run the normal setup.exe outside the x86 folder

if the files are corrupt you may need to restore from a bak.

or you can try mssqlrecovery if you are in dire need.

its a tough price to pay for not...

have you tried to attach just the mdf?

nevermind, i discovered a solution.

I work in a active/passive environment with stand-alone warm backups/logshipping.

I haven't done anything different between each environment.

Fortunately both environments share the exact same partition setup.

i've transfered master between both...moved physical...

Lina,

Try creating a baseline performance output to identify when these spikes are happening. Also, make sure sql is the only thing running on this machine if...

you can use lumigent log explorer to look thru old transaction logs, if security is handled on the sql level.

warren

I'm backing up the databases locally to the shared shelf only.

I'm using a seperate server to copy the backups to a standby along with backing up to tape.

so the clusters...

just one question regarding cpu usage.

should the cpu be above 90% when the transaction logs are being backed up?

there is nothing competing with the backups, and i'm not copying the backups to a network folder from the cluster.

The Full backups have a good return code.

Also, when the transaction...

I can't believe i did that without checking.

Thanks

i disabled builtin administrators last week, but this problem didn't happen until now, why is that?

i understand that the domain account wasn't able to login, when i disabled the builtin...

ok think i've found the problem.

builtin administrators was disabled.

wasn't aware this was needed to run the cluster.

my fault.

our mssqlserver service will not come up, even though we have verified that the password is correct.

it will 'bring online' and we are temporarily able to connect, but then fails.