August 30, 2008 at 8:53 am
Hi all,
I have two doubts with SQL database deployment on target machines.
(1) I want to deploy my software into a client target machine, where there is no any SQL server installed. In that case I may need to install only necessary things into that systems which keeps the sql engine running and so I can make my software working. I think MDAC will do same for MS Access database if same is not installed on target machine. How to make same for (1) MS SQL 2000 and (2) MS SQL 2005?
(2) How to create deployment package in DotNet 2005 (C#) which restores SQL Server database into specified folder along with normal software installation? in this case sql server may not be installed in target machine. If not installed, then we dont have to install SQL server management console (GUI) or query analyzer, only engine or service will be enough for that software.
Please guide me on these two topics...
Thanks in advance.
___
Regards,
Rajeev, India.
August 30, 2008 at 8:59 am
SQL Server is a server service, not a program like Access. It needs to be running for a client to connect. For both your questions, you really need to look at either installing SQL Server Express on the clients, which means you need to handle the install and also maintenance (backup, index rebuilds), somehow. There aren't any tools with Express (like SSMS), so you have to script those things.
You could also use SQL Compact Edition, which is a file based application, and means you include another DLL with your application. However there are restrictions on what features/functions are allowed on Compact edition.
September 2, 2008 at 6:33 am
Rejeev,
You want to do a command line install of SQL Server Express/MSDE. You can include the installers for MDAC and Express\MSDE in your install package. Then you can call a batch file call to do the command line install.
Here's a link about including Express in an install package:
http://coolthingoftheday.blogspot.com/2005/12/embedding-sql-server-express-into.html
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
September 2, 2008 at 7:24 am
Hi,
Thanks a lot Steve Jones and Jack Corbett. I was thinking of using SQL Server Express edition and installed and checked also. But the thing is, I don't want client to open the database tables in the Management (GUI) tool and play with data. With MS Access, atleast we can password protect it, but same can't be with MS SQL! So looking for minimal installation for MS SQL Express edtion with only option for SQL services, backup/restore and other essential services available and programmer can work in Query Analizer.
Thanks for the usefull tips.
September 2, 2008 at 8:02 am
When you run a command-line install of SQL Server Express you can specify that only the Database Engine and connectivity tools are installed so that SSMS Express, etc.. are not available to the user. The only way to stop the user from using Access or some other ODBC tool is through security. Have a strong passwords for sa and your application user, and remove Builtin\Administrators from the sysadmin group or remove it completely.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply