will give that a shot thanks..and i thought each NEW version we to make things easier 🙂 o well...

Well yes the use of SQLSafe(or others) would work but the problem with those are this... i am trying to take the pressure off the production server.  For those softwares to work...

LVL0 = full backup .... LVL1 = incremental backups

Well these are running over a network to a backup server then to a tape library and it goes from there.  Currently using Netbackup and...

your situation as serious as it is.. your explanation leaves TONS of opens holes.. please give more details as to the problem...

slow logins...slow query runs...please be more specific as to...

No multi-instance machines.. all single instances. A few clusters but thats different.

Thanks everyone

Thanks for the ideas. Looks like this will be a time consuming process but o well guess have to get all...

I would make sure that AWE is enabled and then check that you have the memory allocated to SQL to use what it needs as well. Also look to...

The situation has come to an end..finally....after long hard searching and working and ...and...and ..    Anyways..

The SQL Server of the prod and backup...

keeps saying there is an error when redoing logged operation in database 'msdb'...Error at log record id (7603:329:3)

And then after i tried the dbrecover - the logg is could not...

thanks for the suggestion..and i tried using that and still remained in suspect mode.

Now just to add here... this is a backup server.  So currently it has the same msdb...

I am coming in as the sa on both machines.  When i look into the logs the reference is back to Sql Native Client.  And even when its install it still...

AWESOME!!!!!  thanks a TON to everyone that replied.

That worked.. got it going and all...man o man sometimes the obvious is hard to see. Prolly cuz always thinking there has to...

Thanks EVERYONE..... but just figured out the real problem...   Which is a whole new ball of wax 

Trying to install that same SQL 7 instance...

Is it possible to redirect the registry.. or better just to reinstall starting at sql 7 to reach my goals.

Bill,

This i know is true.. but i dont want to accept that... Any ideas or am i just stuck with this situation?  I know i can force it elsewhere ..maybe...i...