Your problems aren't with SQL Server, they are with MDAC and the client software drivers you installed. Since I have no idea of how to correct that part, to me it means wiping the entire server and starting from scratch with an OS install. Getting a backup for SQL Server is the easy part. Stop the service. Take all of the .mdf and .ldf files and copy them off to another server. Then reinstall everything keeping all of the directory structures intact. Once you are done installing SQL Server, stop the service, copy all of the .df and .ldf files back into their former locations and start the SQL Server back up. It should come back alive with every database and all remote servers recognized and working. Of course, this goes with the caveat that you are going to test this process first on another machine.
For More Information
- Dozens more answers to tough SQL Server questions from Michael Hotek are available here.
- The Best Microsoft SQL Server Web Links: tips, tutorials, scripts, and more.
- Have a SQL Server tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical SQL Server questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, SQL Server, DB2, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Dig Deeper on Microsoft SQL Server Installation
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.