Blogs

Off-topic: Claim your blog on Technorati.com

If you are writing your own blog, you might be interested in this information:


Technorati.com is one of the most famous blog directories out there. To increase visibility of your blog, it is a good idea to claim it with them. Go to technorati.com/blog-claiming-faq for the details.


The steps are simple:

  1. Create an account

  2. Login

  3. Click on your username in the upper right corner

  4. Scroll down all the way till you see the “Claim Blog” form

  5. Fill out the form

  6. Technorati will send you an email with a claim code (E.g.: 7VJT4PU99JR6 )

  7. Create a new blog entry containing this code

  8. Repeat steps 2,3 and 4

  9. Click the “Check Claim” button

  10. Click the “Verify Claim Token” button


Now your Blog will undergo a review process, which might take some time, so be patient.

Index Views: IndexPhysical

With this post I am going to start a series about queries that I find helpful while researching indexes and index issues. In fact, because I use them often, I encapsulated them in views.


The first one is SATools.IndexPhysical:


Faking Views

We've seen FakeTable in tSQLt in action in a few demos now. Did you know that you can use FakeTable to fake a view?


You use FakeTable on a table when you want to test a procedure (or function or view) that relies on a table. It prevents you from needing to concern yourself with all of the other constraints a table might have, such as foreign keys to other tables or not-nullable columns which have nothing to do with your procedure. This is particularly useful if you have a schema where many tables are interrelated through foreign keys because you can focus on the procedure you're testing instead of trying to create test data for dozens of unrelated tables.


Similarly, you would want to fake views.

A Working Table Compare Approach

A while back I wrote an article about the underestimated complexity of a table compare algorithm. At the time I did not show a way of how to actually implement such an algorithm.

Over the last couple of weeks I ran into several blog post that lead me to introduce a way to write one now...

Execution Plan Inaccuracies

Execution plans are a great tool when you are trying to performance tune your SQL code. They contain a lot of information about how SQL Server will achieve what we have asked it to do. You can see which way tables are accessed, how many rows are read, where data is sorted and so on. But you have to be careful when using them. You probably already know, that there are two types of Execution Plans. The Estimated Execution Plan you can get, without actually executing the query. This is an estimate of how SQL Server thinks it will execute the query and it is based manly on statistics of tables and indexes. The Actual Execution Plan on the other hand, SQL Server produces while actually executing the query. It contains information about ho much data was actually read and moved around. That the Estimated Execution Plan can be inaccurate is not a surprise, because it is an estimate. But even the Actual Execution Plan can contain vastly inaccurate data...

First entry

We moved the page to a new platform. (again)
We hope it will stay here for a while. It is a fairly complex system, and you will see changes here and there.

Enjoy
Dennis and Sebastian

Syndicate content