Restoring Instance of SQL Server

I have Inherited) a W2003 Server which has Great Plains (accounting) software installed.  

It as well has SQL Server 2005 installed locally, however the databases (including Master) were installed on a no longer accessible SAN.

I have backup (.BAK) files of Master and the databases I need to restore, however since none are installed on the actual SQL Server it will not allow me to even open SQL to perform the restores.

Temporarily to get access to the data I'm going to build a new SQL Server however we need to access the data through Great Plains.

Any suggestions as to how to get the instance of SQL back on the original server?
FarrellFritzAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

arnoldCommented:
The Great Plains app, could be pointed to the new SQL server to which you attach the DB.

The difficulty deals with login credentials I.e. What credentials th app uses if not using integrated security.

The other option after installing sql, start SQL in single user, and then restore the master db from backup.
0
Steve EndowMicrosoft MVP - Dynamics GPCommented:
Hi,

If ALL of the SQL Server databases are inaccessible (including master, model, msdb, and tempdb), then I would recommend installing a new instance of SQL Server (making sure to selected mixed authentication).  It would be faster and easier.

Once you have the new SQL instance, you only need to restore the DYNAMICS databases and company databases. Do not restore the master, model, msdb, or tempdb databases to the new SQL instance.

If the old SQL Server is operational / functional but only the GP databases are innaccessible, you could try detaching the DYNAMICS and company databases and then restoring them to a local drive.  Again, you only want the DYNAMICS database and company databases.

As for security, once you restore the databases, the sa login will have access to everything. If you need to create new GP logins, you can do so. If you get errors creating the new users in GP because the orphaned user records already exist in the databases, you can manually delete the SQL User records from all of the GP databases, and then create the new logins in GP.

Please let me know if this makes sense and if you have any additional questions.

Thanks,

Steve Endow
Microsoft MVP - Dynamics GP
Dynamics GP Certified IT Professional
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.