moving database from one machine to another machine

Question

0.00/5 (No votes)

See more:

i am creating a project in C# which will keep track of records of some product from data base. i wanted to make installer so that it can run easily on other machine. i need to know which database server should i use, so that when i install it on other machine, i do not ask me to install database server separately.any suggestions?

Posted 25-Jul-12 7:13am

Babar_Malik

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

barneyman · Answer 1 · 2012-07-25T15:06:00

Your choice of DB relies on how you want to use it

If it's only a local DB, with no requirement to share the data out then the following are viable

- sqllite
- sql compact

If you need to have one instance that can be shared, then you're looking at

- sqlexpress (and other variants)
- mysql
- firebird
- oracle
etc

The single use versions are extremely easy to deploy

The multiuse are not - they are intrinsically more 'corporate' - as well as deploying them properly (by actually using their respective installers) you should consider integrating into an existing data installation - many corporates will already have SQL installations that are maintained, supported and backed up

Clifford Nelson · Answer 2 · 2012-07-25T14:11:00

Solution 2

The only option I can think of is to use PowerShell remote capability. Of course this requires the target machines to have the PowerShell remote capability turned on. See http://www.windowsitpro.com/article/windows-management-instrumentation-wmi/use-powershell-to-execute-commands-on-remote-machines[^]

Posted 25-Jul-12 14:11pm

Clifford Nelson

Comments

Wonde Tadesse 25-Jul-12 22:08pm

Can you explain how this answer relevant to the question ? Read the question again please.

Clifford Nelson 26-Jul-12 2:43am

I was not sure about the question, but thought that you wanted to run the installer on one machine and install database on another machine.

Hitul Mistry · Answer 3 · 2012-07-25T07:21:00

Solution 1

You should refer

SqlServer Backup/Restore Utility[^]

http://www.codeproject.com/Articles/26390/SQL-Server-2005-Database-Backup-and-Restore-using

Posted 25-Jul-12 7:21am

Hitul Mistry

Comments

Babar_Malik 25-Jul-12 13:33pm

I know this, but i want to the procedure through which i should not require to install sql server or any other database on target machine.

Hitul Mistry 25-Jul-12 13:39pm

You should use
SQL server compact addition.

Tutorial
http://www.mikeborozdin.com/post/Introducing-Microsoft-SQL-Server-Compact-Edition-(Part-I).aspx

Hitul Mistry 25-Jul-12 13:40pm

Your database will be converted to set of .dll files.