SQL Lotter number selector

-
Just a bit of fun with SQL

WITH
    L0 AS (SELECT 0 AS C UNION ALL SELECT 0),
    L1 AS (SELECT 0 AS C FROM L0 AS A CROSS JOIN L0 AS B),
    L2 AS (SELECT 0 AS C FROM L1 AS A CROSS JOIN L1 AS B),
    L3 AS (SELECT 0 AS C FROM L2 AS A CROSS JOIN L2 AS B),
    Nums AS (SELECT TOP(49) ROW_NUMBER()
       OVER(ORDER BY (SELECT 0)) AS n FROM L3 ORDER BY n),
    Choice AS (SELECT TOP(6) n FROM Nums ORDER BY CHECKSUM(NEWID()))
SELECT STUFF( (SELECT ',' + CAST(n AS VARCHAR(10)) AS [text()]
FROM Choice ORDER BY n
FOR XML PATH('')), 1, 1, '')

Popular posts from this blog

AWS DynamoDB vs Azure CosmosDB vs Azure Table Storage pricing comparison

-
Image
Using a db size of 10Gb, and 10% writes and 90% reads. Provisioned databases are for 1 year. For AWS SimpleDB the amount of CPU is hard to quantify, so I used the following formulae (0.248+((requestsPerSecond)/1.5*0.14))*usdgbp This matches closly to Azure Table Storage, which is to be expected. Here are the results: (click on image to view) (click on image to view) Zooming into the lower end (click on image to view) Download Azure-CosmosDB-pricing.xlsx spreadsheet here . Summary:   Both AWS and Azure are similar in NoSQL pricing. For the small companies out there needing the cheapest NoSQL options there is Azure Table Storage and AWS SimpleDB . These are the cheapest up until you hit 400 reads per seconds which is plenty for most companies. However, be aware of the per-item size constraints below. Table Storage is about 13ms for a read and CosmosDB is about 8ms. Many developers use Amazon SimpleDB in conjunction with Amazon Simple Storage Service (Amazon S3). Amazon Sim...
Read more

SQL Server MAXDOP and parallelism

-
Image
At our company, we have a 4 core blade running SQL Server 2008 Enterprise Edition. This is a very, very busy SQL Server and is running on HP EVA hardware, so the I/O is not an issue. We have over 50 warehouses all running SQL Server 2008 and replicating data to/from this primary database. This database is also used by our website, webservices and import/export applications. The only thing this database does not serve is our SSRS reports, which are hosted on another blade. What is an issue, however, are the CPU's. They were very busy. To help with this we can play around with two settings on SQL Server: MAXDOP (Max degree of parallelism) Cost threshold for parallelism Our DBA and I had a few discussions around this recently. Read plenty of articles on it, such as Adam Machanic On a normal system, leaving these settings alone are fine, but on a very very busy system you need to change them. MAXDOP=1. What this does is to always use 1 core for the query. MAXDOP=0, Cost...
Read more

Setting the PowerShell execution policy - the trap

-
I was recently pulling my hair out trying to run a powerShell script in VisualStudio. I kept getting the error: "File SomeScript.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details." So I ran the script: powershell set-executionpolicy remotesigned Tried a gain, and still it fails! Only until I spoke to my developer collegue Damian Powell did he say you actually have to run that command for both x86 and x64 powershells. So I ran: C:\Windows\System32\WindowsPowerShell\v1.0\powershell set-executionpolicy remotesigned C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell set-executionpolicy remotesigned Hey presto! All works. Thanks Damian!
Read more