|
|
-
Mike Lewis Commented 6 Months ago through Blogs | 1 Point
As with anything it depends on the situation, and it's always worth checking that the compression overhead is worthwhile for each scenario. I actually wanted this originally when capturing the query cache data in SQL Azure - I wanted to compress the st...
|
-
Mike Lewis Commented 6 Months ago through Blogs | 1 Point
I have and will probably do something like that for on-premise, however i'm currently working on sql azure which doesn't support CLR functions. My other option is to make use of the. net libraries in powershell but that would mean using powershell for r...
|
-
Mike Lewis Commented 6 Months ago through Blogs | 1 Point
Thanks. I experimented with passing keywords too, forming part of the Huffman tree like the individual characters. I figured that repeated words reduced down to bit sequences would save a lot of space - I was wrong! I didn't actually get much more c...
|
-
Mike Lewis Posted 6 Months ago through Blogs | 10 Points
I wanted to find a way to save space when storing text in Windows Azure SQL Database. On-premise SQL Server allows page and row compression, which is currently not available in the cloud. ...
|
-
Mike Lewis Commented 6 Months ago through Blogs | 1 Point
It is worth noting that detaching a database clears the query cache, so use with caution. Option #1 above is the recommended method of moving databases. There are also potential file permission issues with detaching databases. I cover it here: [http:...
|
-
Mike Lewis Posted 11 Months ago through Blogs | 10 Points
SQL Azure differs significantly to the typical on-premise solution, and must be monitored and administered with “new thinking”. Index fragmentation is one of the areas where a DBA must scrap the instruction manual and start again....
|
-
Mike Lewis Commented 2 Years ago through Blogs | 1 Point
Absolutely right, the entire transaction is rolled back. But it's worth noting that any violation of a constraint would have the same effect, such as a duplicate value into a column with a unique constraint/index, or violating a check constraint. This...
|
-
Mike Lewis Commented 2 Years ago through Blogs | 1 Point
Absolutely right, the entire transaction is rolled back. But it's worth noting that any violation of a constraint would have the same effect, such as a duplicate value into a column with a unique constraint/index, or violating a check constraint. This...
|
-
Mike Lewis Posted 2 Years ago through Blogs | 10 Points
My question in the recent Beyond Relational BI Quiz (see http://beyondrelational.com/quiz/sqlserver/bi/2011/questions/132/use-of-foreign-key-constraints.aspx) sparked a bit of debate about Foreign Keys, and whether they should b...
|
-
Mike Lewis Posted 2 Years ago through Blogs | 10 Points
My question in the recent Beyond Relational BI Quiz (see
http://beyondrelational.com/quiz/sqlserver/bi/2011/questions/132/use-of-foreign-key-constraints.aspx)
sparked a bit of debate about Foreign Keys, and whether they ...
|