Page 3 of 3 FirstFirst 123
Results 21 to 26 of 26

Thread: MSSQL Error

  1. #21
    Join Date
    Feb 2009
    Location
    Somewhere in Vermont, USA - unless I'm not
    Posts
    9,517

    Default Re: MSSQL Error

    Hi -

    The standard way of setting up a db in MS SQL is to crate a new DB - Call it "Dennis" or "Water" or "Breakfast" - IOW, whatever you want. Then put all your tables in that DB. Master is saved for system stuff.

    SQL instances (you have an "instance" of MS SQL on your machine) are different from the embedded DB in that you can have any number (within reason) of different DBs in them. So - the Dennis system could connect to the Dennis DB & Hyannis could connect to the Hyannis DB, PTown to the PTown DB, etc. Each DB has its own table structure (though the structure in Dennis might be the same as PTown - just different data) and changes made in one will not change anything in the other.
    Garret

    All my life,I always wanted to be somebody. Now I see that I should have been more specific.


  2. #22
    Join Date
    Feb 2009
    Location
    Adelaide, South Australia, Down under
    Posts
    2,223

    Default Re: MSSQL Error

    Quote Originally Posted by Tremain Fernandes View Post
    Ok I will do that, back and restore with a better name but I don't understand you last statement?
    Hi Tremain
    What I mean is now master has the two table sets let’s call them ‘server’ tables and ‘application’ tables.

    The end state you want is for the master to only have ‘server’ tables and the application database to only have ‘application’ tables.

    So after you backuped master and restore as xyzdb you have two complete sets and therefore some dropping of tables to do, to get to that desired end state.

    Cheers
    Marco
    Marco Kuipers
    DataFlex Consultant
    28 IT Pty Ltd - DataFlex Specialist Consultancy
    Adelaide, South Australia
    www.28it.com.au

  3. #23

    Default Re: MSSQL Error

    I'm having trouble restoring the master with a new name. can only do it in single user mode and it won't let put the master in single user etc. so I think the simplest solutions is to just reconvert a backup embedded DB to SQL again only name it properly this time.

  4. #24
    Join Date
    Feb 2009
    Location
    Somewhere in Vermont, USA - unless I'm not
    Posts
    9,517

    Default Re: MSSQL Error

    Leave the master, remove your tables from it, create a new DB & convert the embedded tables to the new DB.

    Make sure you only remove your tables! If you get rid of any system ones, bad things will happen.
    Garret

    All my life,I always wanted to be somebody. Now I see that I should have been more specific.


  5. #25
    Join Date
    Feb 2009
    Location
    Peoria, IL
    Posts
    5,291

    Default Re: MSSQL Error

    Like Marco says your application tables should be in their application database. It's technically okay to have some user tables in master if they are shared across application databases. We have a couple of those.
    Chuck Atkinson

    All generalizations are false, including this one - Mark Twain

  6. #26
    Join Date
    Feb 2009
    Location
    UK
    Posts
    662

    Default Re: MSSQL Error

    As Chuck stated you can add tables to the Master database, but in my experience it is not common practice.

    Your application can login to more than one database at the same time, on the same server or on different servers. One of the applications I am working on currently connects to 8 databases. It always logs into the main database which has user, security info, etc and then logs into the other databases as required. You just need to give each database a different connection ID
    Ian Smith
    (Member of the SigCj project)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •