SQL database in master

I've realised that a database we've been running ended up inside the SQL
2000 master schema, and not in the separate database as was planned. I
remember clicking through the application installer options and thought I
did tell it to use the new database I created instead of master, however,
the master schema is the one that's got all of the applications tables and
growing in size, whilst the separate database is only a couple of hundred
kb.

I am wondering, is it relatively easy to move the application to the
intended database (on the same SQL server) or is it normal practice to leave
things in the master schema? Should I move it out of master?

I'm relatively new to SQL server so any help is appreciated.!


.

Relevant Pages

  • Re: script to find all parent records that have references in at least one table.
    ... separate database. ... a good half of the records we want to move most likely has references ... within its database. ... but I forgot to ask: which version of SQL Server are you on? ...
    (comp.databases.ms-sqlserver)
  • Re: dbdebunk Quote of Week comment
    ... > a lot of really bad SQL programmers. ... But SQL does not have a pointer data type or the ... > being told to design a database. ... But why is little Cindy Lou Who employee ...
    (comp.databases.theory)
  • Re: DBMS and lisp, etc.
    ... Naively implemented with SQL, again for 10 ... (1 query for the initial orders, 1 query for each order for its ... soon as you upgrade to the SQL database. ... (eq (order-customer orderA) ...
    (comp.lang.lisp)
  • Re: dbdebunk Quote of Week comment
    ... > a lot of really bad SQL programmers. ... a surrogate key should support the primary key. ... But SQL does not have a pointer data type or the ... > being told to design a database. ...
    (comp.databases.theory)
  • Re: dbdebunk Quote of Week comment
    ... But SQL does not have a pointer data type or the ... More and more programmers who have absolutely no database training are ... But why is little Cindy Lou Who employee ...
    (comp.databases.theory)