Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The project I’m working uses SMO to restore the needed databases as part of the application installer. The problem is, on a machine that has never had the application installed.
From the event logs, it seems like the database can’t be restored because it doesn’t exist in the instance. (Due to the fresh install)
Can I use SMO to restore the database to an instance where it doesn’t already exist? Is there a best practice for installing databases this way?
Have you thought about maybe just using smo to attach the database on new installation, assuming you already have the .mdf/.ldfs and related paths?