4x AWS Certified. Pluralsight & Packt Author, CTO, Software Architect, Team Leader, Tutor, Speaker, and Software Developer. I like to create fast, scalable solutions using AWS, Azure, C# and SQL Server.
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...
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...
I had a problem recently trying to search the Skype instant messeage history. Searching for a historical chat can be done in Skype by pressing CTRL-F, but only if you know the person(s) that were involved on that chat. You cannot search the chat history globally. The solution is to dump out the skype database into a TXT file for easy searching with notepad. Download SQLite command shell at http://www.sqlite.org/download.html. (I downloaded http://www.sqlite.org/sqlite-shell-win32-x86-3070400.zip ) Extract sqllite3.exe to a place on your path, or somewhere you can run it easily from. Open a DOS command prompt. Change the folder to C:\Users\[pc user name]\AppData\Roaming\Skype\[skype user name] There you should find main.db database. Type the following (in bold): sqlite3 main.db sqlite> .output c:\skype_chat.txt sqlite> .dump sqlite> .quit You can now start Notepad and open file c:\skype_chat.txt to search through.