I have the full version of SQL Server installed on my machine and am developing an app using BI DTS packages, VB.Net, SQL SPs, etc.. I will need to deploy this app w/SQL Server Express (SSE).
-Do I have to install SSE on my development machine for the purpose of creating the install package of my application? I am afraid that if I do install SSE on my machine, it may mess up my installation of the full version of SQL Server... will it?
-Can you point me to a link with information about how to do the development with the full version of SS, and create the installation package using the SSE?
Thanks for your help.
Steph
You cannot deployment SQL Server 2005 Integration Services packages in SQL Server Express because the runtime now comes with the server license. In SQL Server 2000 the DTS package comes with the runtime that changed in 2005. Hope this helps.|||Thanks for the response.
The way I posed my question was misleading. I'm sorry about that. I shouldn't even have mentioned the DTS packages.
The big picture of the app is this:
- Data resides in a datamart at a central office. The central office will be running the full SQL Server 2005 version (this is where the DTS packages reside and run).
- Satellite (very small) offices need to download updated information relating to them from the central office. I'm thinking of having these satellite offices run SQL Express.
I'm developing the code to update the satellite office data from the central office data. On my development system, I am running the full version of SQL Server 2005. Should I also install SQL Express on my development system ? Will it mess up my full SQL Server 2005 installation?
Thanks,
Steph
|||It is tricky but here is how you could do it legally create Asp.net application run it from your main office SQL Server create a job to execute the many versions of the package make your small offices destination. It will take more work but the alternative solution may cost you more hardware SQL Server Express can be a subscriber in replication so you can push the data with replication. You could always talk to your local Microsoft SQL Server contact person, in some areas there is regional contact person. Hope this helps
No comments:
Post a Comment