SQL DB Deployment

Hi all,
I've developed an application that's using SQL Server for DB, now I want to create a setup and give it to users.
For the DB part, I have a simple '.mdf' file that is created with SQL Server and connecting to it like this:

sql_conn = new SqlConnection(@"AttachDBFilename=c:\test.mdf;Integrated Security=true");

then it's a simple connection; but I don't know how to use my DB in the user's computer, I should only copy the .mdf file in the user's computer? what's the exact steps to deploy a SQL DB related application?
I've searched the Internet and some eBooks + MSDN but didn't find anything about that.
I'm working with C# 2.0 WinApp in VS2005 and it's for XP or Vista.

Please answer soon, since I want that in a week.
Thanks in advance.

Assuming there was no associated log file (.ldf), then copying the .mdf to the target and "attaching" to it is usually sufficient.

The alternative is to make a backup of the mdf file,and then "restore" it into the new server.

Some minor tradeoffs between the approaches, but both are common....

Quote:

---

Originally Posted by Promotional Engine

... I should only copy the .mdf file in the user's computer? ...

---

Aside from TheCPUWizard's suggestion, of course you need to install Sql Server in the target machine also assuming it is not yet installed...

Thanks guys,

TheCPUWizard, can you explain the steps and statements in C# 2.0 to attach or back&restore a DB?

dee-u, the user should have SQL Server installed?! :eek: It's practical? I don't think it's the way that current apps are going! Please tell me what should be installed on the target machine and how to install that with an installer like .NET Setup. :cool:

Thanks. :)

1) The steps are NOT (typically) done fromwithin the application.

2) YES SQLServer needs to be installed on the machine. The MSI should be launched from within your own installer.

Quote:

---

Originally Posted by Promotional Engine

...It's practical?...

---

It is a requirement... :)

May I add that if it is going to be in a multi-user environment then you should just install in one machine and access the database from there...