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

Service Broker sys.transmission_queue clean up

-
If you’re developing a Service Broker application and you misspell your services, forget to create a master key, or do any of the many things that result in your messages not being delivered, then your transmission queue will fill up. Due to the nature of service broker, errors don't occur at the client but rather your messages go in to Service Brokers sys.transmission_queue and are then subsequently processed. If they fail, they stay in the queue. Some errors can be resolved, i.e. missing services. However, others can't, or are just plain difficult. I.e. You've misspelt something, or not used the correct security. To clear your transmission queue you need to end the conversations, this is a handy little script for doing this. Be aware this ends ALL conversations in the queue and so should NEVER be used on a production system. To see how many messages are in your transmission queue, use this SELECT   COUNT ( 1 )   FROM   sys . transmission_queue On my system i7, D...
Read more

AI Reading comprehension scores

-
Image
In September 2019 there was a great many blog posts about AI surpassing human reading comprehension scores. Humans comprehension of a piece of text is 89.452% As of June 4th 2021, AI is now hitting scores of 93.214 , by IE-Net (ensemble) - RICOH_SRCB_DML Plotting the scores on a graph: Extrapolating the scores, we should see an AI hit 100% sometime in 2021. Spreadsheet I created for the graph above: AI-Comprehension-score.xlsx Original data source: https://rajpurkar.github.io/SQuAD-explorer/ Also see https://paperswithcode.com/sota/question-answering-on-squad20
Read more