Compartilhar via

** More mind shift info **

  • Artigo

I should also point out that in VS Beta 1/SQL Beta 2, this Xcopy functionality is limited to those with admin rights.  In the next beta, non-admins will have Xcopy capabilities as well.   So, joe user that gets my app and database, that is a normal (read: non-admin) on his machine, will be able to run his app directly as well. 

Some have asked questions about security threats, etc.  By default, SSE has networking turned off.  The default authentication mode is NT Auth. 

Think of SSE as your starting point for database application development.  It's very easy to use and, it *is* SQL Server.  When your app grows up beyond single machine needs, and you want to turn networking on, or move it to a full fledged SQL Server installation -- it's a simple painless conversion.  Depending on what you want to do you either just turn networking on for SSE or you move your MDF to a server and attach it (and change the connection string in your app's config file.)

Comments

  • Anonymous
    June 30, 2004
    The comment has been removed
  • Anonymous
    June 30, 2004
    Ronny, I had follow up your post on the previous post (see the link)

    http://blogs.msdn.com/vsdata/archive/2004/06/29/169288.aspx#170602


    Thanks,

    -Ming
  • Anonymous
    July 01, 2004
    Generally, it will be such that if the user has write access to a physical location, the user will have the ability to access to the MDF. The thing to keep in mind here is that all of the corner scenarios can be handled with existing functionality. Xcopy capabilities do not replace existing functionality, they agument it. The scenario that is more fully enabled with Xcopy is the quick start scenario and the specific knowledge necessary to make it work. It's a removal of a barrier to entry and start.