c# - What are in SQL Server User Instances that make them impossible in non-Express Editions? -
after developing few years (or more), still not understand:
- what makes user instances impossible/incompatible developer (or other) edition of sql server?
- why has developer install more 1 (i.e. developer edition) of sql server because user instances available through express edition?
update: @damien_the_unbeliever wrote in answer,
do understand correctly user instances:
- require sql server express setup
- cannot connected remotely
- the user cannot have more 1 such instance?
- the client apps connect them dev tools vs, ssms, webadmin, sql express utility, etc?
really not understand when/why/how can used/deployed outside of development environment
what non-dev cases of sql server user instances (vs ce , other embedded databases)?
i don't believe there technical reasons why user instance functionality couldn't exist in other editions - non-express editions represent different form of expected usage.
user instances pretty expected standalone databases, used single application, , meaningless without application.
databases under standard/enterprise edition expected maintained (possibly dedicated dbas) standalone resources, maintenance plans, scheduled jobs, etc. they're expected use additional features of these editions, , wouldn't make sense single application control availability of these databases.
and developer, need both installed if you're working on systems in both usages make sense - both building small scale websites simple data requirements, , larger systems need more complex database systems.
the "typical" example of application use user instance, not being dev tool, small web application. may have 1 or more mdf files in it's app_data folder. may run such services membership system such db. advantage of such setup xcopy deploy of such website sufficient entire application ready - connection string valid immediately.
Comments
Post a Comment