like MS access, you can have an MDB file that can be used by simply
specifying in the connection string where to find the file and the JET db
engine can get it.
it would be nice to have a similar situation where (maybe minus the
flexibility of putting the db file wherever you wanted) you could put the
database and transaction log files into a certain directory on a SQL server
or MSDE installation and have the database be instantly available. AND
address the issue of sysuser SID's not matching up in the msdb table [which
is an issue I think is a little absurd]
here's what i'm thinking:
1. grab any of the .mdf and .ldf database files required for operation
2. move them to the production sql server's databases directory. (obviously
user A shouldnt be able to kill user B's databases, if multiple users can
use the server, this could be addressed with ACL's)
3. simply reference the main mdf file: "use databaseA". the use operation
can bring the database online and let SQL server read any meta data it needs
to be able to bring the database online, fully secured and such.
4. the database context is established [or fails because security couldn't
5. sql server carries on like normal
I'm making this assertion in the sprit of .Net programming: xcopy
deployment. For instance, being able to "copy the database" onto the
hosting provider's sql server would bring SQL server's ease into the
territory of Access and MYSQL.
would that be great?