Best way forward for system that requires its own instance?

  • My client went shopping and bought a system designed for use in the US after being told it would work in the UK.

    When I installed the database it turns out it uses US collation. The application however fails with collation errors because it uses tempdb which is in the UK collation, why wouldn't it be!

    My client is adamant that the system is still fit for purposes and that I (just) need to change the IT infrastructure to suit the system and all will be well. 😉

    So, given that the current SQL setup consists of a SQL server, mirrored to a remote site and a test server, is the only option to setup three additional servers?

    It's such a PITA because the database is only around 600MB!

  • You could setup a second named instance on the server that would have the correct collation.

    If you have access to the code you could modify the code to use the COLLATE hint when using tempdb which will of course affect performance.

  • In addition to Jack's ideas, you could go virtual if there isn't a large load on the system. Named instances as well, if you have the memory to support them.

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

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