Surprising SQL speed increase

-
I’ve just found out that the execution plan performance between the following two select statements are massively different:

select * from your_large_table
where LEFT(some_string_field, 4) = '2505'

select * from your_large_table
where some_string_field like '2505%'

The execution plans are 98% and 2% respectively. Bit of a difference in speed then.

There are lots of places in our SQL where we use LEFT(something, x) = 'string'
This should be replaced by the LIKE command for greater speed.

I actually found this out by checking the LINQ generated SQL against my hand crafted SQL. I assumed the LIKE command would be slower, but is in fact much much faster.

Popular posts from this blog

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

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

Execution of user code in the .NET Framework is disabled

-
I was testing our new SQL Server 2008 enterprise cluster today and managed to get the following SqlException running a C# application: "Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option. The statement has been terminated." The solution is to run the following: EXEC sp_configure 'show advanced options' , '1' ; go RECONFIGURE ; go EXEC sp_configure 'clr enabled' , '1' go RECONFIGURE ; -- Turn advanced options back off -- EXEC sp_configure 'show advanced options' , '0'; GO
Read more