Creating SQL Server Databases With No Security Restrictions

From: Peter van der Goes (p_vandergoes_at_toadstool.u)
Date: 02/08/05

  • Next message: Simo Sentissi: "Business intelligence training and Cert from Microsoft" 
    Date: Tue, 8 Feb 2005 10:10:23 -0600

    First, let me apologize for crossposting and the lengthy post, but this
    question involved both MSDE and (I believe) security settings.
    We use Visual Studio .NET 2003 with MSDE in classrooms and labs and have
    had no security issues once things were configured properly for student
    access. The sample databases install and work correctly for any authorized
    users who might be logged on to a given PC.
    We are using a text that supplies .mdf files as part of the support
    materials for the book. We are able to copy the .mdf files to the
    appropriate directory (..\Microsoft SQL Server\MSSQL$InstanceName\Data),
    then use Server Explorer in VS .NET to create a database link to the file
    (Connect To Database button on the Server Explorer toolbar). Once VS .NET is
    restarted, the database appears in the list of databases under the SQL
    Server instance and is fully accessible.
    I now want to create additional SQL Server databases for students to use
    with development projects, etc. I have access to the SQL Server GUI
    management tools (from our MSDNAA subscription) and they are installed and
    working with the MSDE instance on my office PC. When I create a
    database/tables/etc. on my instance, then attempt to copy the .mdf to
    another PC to use the setup technique described above, a window pops up
    wanting me to select a security option and then refuses me access to the new
    database regardless of the option (NT Security or database
    username/password) I try to choose.
    After all that, what I'm seeking is the way to create a database to export
    to any PC, with any student or faculty member logged on so that they can
    import the .mdf file and connect to it using Server Explorer *without*
    encountering security issues. So, when I'm creating a database, what
    settings do I apply so that it doesn't care who is interacting with it?

    Thanks in advance for reading and any insights!

  • Next message: Simo Sentissi: "Business intelligence training and Cert from Microsoft"

    Relevant Pages

    • Re: setting a password on a button on the switchboard
      ... Could you send me the sample database for the fourth option (4. ... > Security in an Access database can probably be broken down into two big ... > points about being easier than User Level Security, ... > What type of data are you trying to protect? ...
      (microsoft.public.access.forms)
    • Re: access 2003
      ... security in access 2003. ... The data will go on the server and the program database ... than the alternative of creating an mde file. ... MDW file from the written record. ...
      (microsoft.public.access.conversion)
    • Re: SQL or Access DB
      ... i am aware of the security modell of SQL server (we do use SQL server ... an end user,,, there is not reall alternative as a worgroup Access database ... MSDE and SQL express are all free ...
      (microsoft.public.dotnet.languages.vb)
    • Re: access 2003
      ... security in access 2003. ... The data will go on the server and the program database ... than the alternative of creating an mde file. ... MDW file from the written record. ...
      (microsoft.public.access.conversion)
    • Re: Is this possible??
      ... I understand Windows security but since I've not seen A2007 live, ... The backend is on the server in it's own file. ... database, but everyone does not need to have access to tblwage which is ...
      (microsoft.public.access.tablesdbdesign)