11 reputation
1
bio website virtualenergymanager.com
location
age
visits member for 2 years, 6 months
seen Aug 28 at 12:37

May
8
comment Is it OK to create hundreds of databases in SQL Azure versus one big one and run the risk of deadlocking
The deadlocking which I have experienced in the past - is that many different teams in many different ways have been accessing this data in the past - with disastrous consequences. Hence, I have been drawn to the elegance of separating the sites into different databases - and having a single application thread which is allowed to write data into it. Reads of the data can be dirty - and I am tempted to allow READ UNCOMMITTED as the default transaction state when connecting to the DBS for reading.
May
8
comment Is it OK to create hundreds of databases in SQL Azure versus one big one and run the risk of deadlocking
That would imply a generic decimal(10,3) would suffice.
May
8
comment Is it OK to create hundreds of databases in SQL Azure versus one big one and run the risk of deadlocking
Current projection is about 200 sites per year - keeping the data for at least one year. I am getting a representation of a signed 32 bit integer from the site of which the maximum number of decimal places will be 3.
May
8
comment Is it OK to create hundreds of databases in SQL Azure versus one big one and run the risk of deadlocking
I find your comment about the 150GB db size for Azure quite an important one - as we will definitely have more than 150 engines - hence more than 150GB data.
May
8
comment Is it OK to create hundreds of databases in SQL Azure versus one big one and run the risk of deadlocking
Thanks for the reply, the messages from the remote sensors are going to be coming in through an XML packet - passed off to a service bus (currently MSMQ) and then processed by an application thread. I was going to either: 1. Have muliple threads/proceses all accessing the DB at the same time (hence my deadlock worry scenario) or 2. Have an application process/thread per database and never need to worry about deadlocking as each application will only be writing to a single db
May
4
awarded  Student
May
4
asked Is it OK to create hundreds of databases in SQL Azure versus one big one and run the risk of deadlocking