|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL CE - Multi-user
If a SQL CE database is deployed on a file server, is there a way to block
the second user from accessing it? (preferrably without the use of a separate "KEEP OUT" file that would be created after the first user accesses the database) I know this isn't a great deployment scenario, but I am dealing with an existing application and am exploring some options. Thanks. "arothberg" <arothberg@newsgroups.nospam> wrote in message Set the database properties to single-user.news:326BEBD5-5ED5-4487-A3A2-8D18E2B03F70@microsoft.com... > If a SQL CE database is deployed on a file server, is there a way to block > the second user from accessing it? (preferrably without the use of a > separate "KEEP OUT" file that would be created after the first user > accesses > the database) > > I know this isn't a great deployment scenario, but I am dealing with an > existing application and am exploring some options. > I don't understand this reply. Please clarify. SQL Server 2005 Compact
Edition is only supported for single-user. To my knowledge, there is no option to turn if "off" or "on" Show quoteHide quote "Bob Simms" wrote: > "arothberg" <arothberg@newsgroups.nospam> wrote in message > news:326BEBD5-5ED5-4487-A3A2-8D18E2B03F70@microsoft.com... > > If a SQL CE database is deployed on a file server, is there a way to block > > the second user from accessing it? (preferrably without the use of a > > separate "KEEP OUT" file that would be created after the first user > > accesses > > the database) > > > > I know this isn't a great deployment scenario, but I am dealing with an > > existing application and am exploring some options. > > > Set the database properties to single-user. > > > In your connection string set file mode to exclusive.
Show quoteHide quote "arothberg" <arothberg@newsgroups.nospam> wrote in message news:326BEBD5-5ED5-4487-A3A2-8D18E2B03F70@microsoft.com... > If a SQL CE database is deployed on a file server, is there a way to block > the second user from accessing it? (preferrably without the use of a > separate "KEEP OUT" file that would be created after the first user > accesses > the database) > > I know this isn't a great deployment scenario, but I am dealing with an > existing application and am exploring some options. > > Thanks.  
Other interesting topics
SQL Server Small Table Performance Problem
Default Database? non unicode Urgent please help!! Restore failed for Server (Microsoft.SqlServer.Smo) SQL Server 2005 - Checking startup account from TSQL Dumping sql server OODBMS vs RDBMS Restoring Transaction Logs Into Backups of MDF and LDF Cannot delete maintenance plan. Multi-user issue |
|||||||||||||||||||||||
