SQL 2008 database location,

This topic contains 6 replies, has 3 voices, and was last updated by  rajeshpl 1 year, 8 months ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts

  • michasio
    Member
    #166937

    Hello,

    May I ask You for help?
    I going to install new SQL server on the new hardware.
    On old server I have 4 databases located in the same folder.
    I want to put 2 databases in one folder (first partition), and next 2 in other folder (second partition).
    Can I set up 2 different location at installation process?? Or should do it after installation?

    Second question, Can I change instance name after database restore?. I want to have the same name.

    Regards
    michal


    Ossian
    Moderator
    #191596

    Are these the system databases? If so, they will all go into the location you specify for databases during setup, but you can move them afterwards

    According to MSDN changing the instance name is not supported, but apparently you can do it (https://sqldbpool.com/2008/09/03/how-to-change-sql-server-instance-name/)


    rajeshpl
    Member
    #391512

    Hi,

    Ok. thx for answer.
    But as You said, i can change location… Can I put for example 2 databases in one partition and next 2 databases in other partition ?

    regards
    m


    Ossian
    Moderator
    #191597

    WHat databases are you wanting to move?
    If it is the system ones, do you really need to?

    The main performance gain you can get is separating logs from databases onto separate disk arrays


    rajeshpl
    Member
    #391513

    Hi,

    i want to change location of the ERP database.

    michal


    Ossian
    Moderator
    #191600

    Yes, no problems in putting multiple databases in multiple locations.
    However, review guidance and best practice on separating databases and logs, and investigate how many disk spindles you have available (NOT partitions) before you start moving things.
    The biggest performance improvements are from separating databases from logs and placing the logs on the fastest possible (but still highly available) disk arrays.

    Basically, if you don’t know exactly what you are doing, and the potential consequences, do NOT change anything – in SQL server, the potential to FUBAR things is much higher than in other products.


    rajeshpl
    Member
    #391515

    Everything completed successfully.
    Thanks for help.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.