Printable View
does anyone have any info on how to include the msde with an application and how to setup the databases for the end user prior to them using the application? preferably in the background without them seeing this.
also, how do you include the engine with a setup package?
You would have to include the MSDE setup installer within your install package ( CustomAction for VS Deployment packages).
You could then use vbscript to attach the mdf file to the newly installed sql server.
It would all work best if they had a SQLServer already installed though...
righto. unfortunately, sql server doesn't come cheap. i dind't know that msde saved the databases as mdf. interesting.
you dont need SQL Server at all for MSDE, that is the whole point of MSDE
thats what he meant. if the end user already has SQL server, it would be better than having to include the msde and all the jazz that's involved.
well you probably won't do that very easily "behind the scenes". If a company already has SQL Server running, I would hope they had a DBA or someone who at least knows what they are doing (IE not an end user) in charge of that DB. Your app probably would not install on it as it would need permissions, etc.
You are better off just using MSDE with the app. The only place it will be more cumbersome would be when having people DL your app, because it will add to the size, but as far as distribution on CD, its really no issue
Have you looked at the SQL-DMO at all for setting up the database once it is installed?
what's the sql-dmo?Quote:
Originally posted by SeanGrebey
Have you looked at the SQL-DMO at all for setting up the database once it is installed?