When using Windows Azure Pack(WAP) to provide multi-tenant Database as a Service (DBaaS), new databases are created with collation I don't want

  • Hi All,

    This is a Windows Azure Pack configuration question rather than specific to SQL 2014 but there doesn't seem to be a more relevant section to put it in.

    I've setup WAP infrastructure and presented the SQL fabric in order allow users the ability to self serve either SQL on a VM or just create a PaaS database (DBaaS SQL Azure db style but in our private cloud).

    Everything seems to be working as expected except when the user creates a database it is created with the SQL_Latin1_General_CP1_CI_AS collation rather than the Latin1_GENERAL_CI_AS collation that SQL is configured to use.
    There must be a configuration setting within WAP where the collation is set and uses this as the template for the db creation script but i've no idea where it's stored and what the supported way is to change the value.

    Anyone know the answer ?

  • No clue, but push comes to shove, you can create an ALTER DATABASE command to change the default collation and use that script prior to any tables being created.

    Steve (aka sgmunson) 🙂 🙂 🙂
    Rent Servers for Income (picks and shovels strategy)

  • sgmunson - Friday, July 21, 2017 10:48 AM

    No clue, but push comes to shove, you can create an ALTER DATABASE command to change the default collation and use that script prior to any tables being created.

    True, but this is supposed to provide an automated self service experience.
    Not exactly seamless if that's the only option 🙂 

    I logged a call from Microsoft over a month ago, still no definite answer yet but from the noises they're making it doesn't sound like it's configurable.
    As WAP isn't exactly a volume product I doubt they'll be rushing to change it 🙁

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

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