providing sql database with you're application install for customer side
-
hi i am developing an application that is using sql server 2005 and its database, i am wondering that how can install my application on the customer side that works perfectly with sql server? i don't think that i should install Microsoft SQL Server on the customer side, shall I? so what should i do ? is it enough to install microsoft sql native client on customer side?
-
hi i am developing an application that is using sql server 2005 and its database, i am wondering that how can install my application on the customer side that works perfectly with sql server? i don't think that i should install Microsoft SQL Server on the customer side, shall I? so what should i do ? is it enough to install microsoft sql native client on customer side?
The only configuration when you don't need to install SQL Server is when you use compact edition, which is intended for local single-user systems as a small database. If you use Express edition or higher, SQL Server installation is needed.
The need to optimize rises from a bad design.My articles[^]
-
The only configuration when you don't need to install SQL Server is when you use compact edition, which is intended for local single-user systems as a small database. If you use Express edition or higher, SQL Server installation is needed.
The need to optimize rises from a bad design.My articles[^]
-
i have used enterprise edition, you mean that i have to seperately install sqlserver and then install my app?
Well, if you use Enterprise Edition, the first thing is that it's licensed pruduct and the customer must purchase the license in order to use that edition. When the licensing part is managed, then you would install the SQL Server (or the customer installs it beforehand) and after that in a separate installation you would install your application. I'm not sure if there's a way to link these installations, but the most important point is that you cannot distribute Enterprise Edition with your application without the customer having a valid license.
The need to optimize rises from a bad design.My articles[^]
-
hi i am developing an application that is using sql server 2005 and its database, i am wondering that how can install my application on the customer side that works perfectly with sql server? i don't think that i should install Microsoft SQL Server on the customer side, shall I? so what should i do ? is it enough to install microsoft sql native client on customer side?
No you shouldn't include the SQL Server install as part of your install. Usually when SQL Server comes into play it is installed and configured as a seperate task. As mentioned before, a license would need to be purchased to use the product on the up and up. The sequence in which you install your application doesnt not matter, you will just need to know the specifics of the SQL Server and your application would then be able to connect. In the past I've just had a SQL Svr property page in which you define the svr name, logon parameters, database name and port. Schott