Collation issue with multiple dbs

  •  We are going to be migrating our production dbs from SQL2000 to SQL2005 as well as purchasing a new finance system. The new system database requires a different collation than the default that all of our other dbs use. I was thinking this may be a good reason to put two instances of sql 2005 on the new server...One for the new finance system and another for everything else. I'm not sure what the pros and cons of doing this may be...does anyone have any experience with this or can tell me if I'm approaching this the wrong way?

    Thanks!

    Thanks!

  • That is very good planning because most financial software use BIN(binary sort order) the fastest sort in SQL Server, the problem with BIN is require all data to be case sensitive, which means queries also must be case sensitive.  Your plan isolates case sensitive requirement to an instance just serving the financial software.

     

    Kind regards,
    Gift Peddie

  • Thank you for the response...and yes they require case sensitivity..augh!

    I was also wondering if there are any known issues with having two instances in a clustered environment (active/ passive)?

    Thanks!

  • No I looked in the BOL you can install many instances in one box, now cost you have to check with licensing in your company.

     

    Kind regards,
    Gift Peddie

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply