The Bit Bucket

There are lots of reports of data quality services (DQS) not working after installing CU1 for SQL Server 2012. One symptom is that when trying to connect from the DQS client, you receive the following error: “System.Data.SqlClient.SqlException (0x80131904): An error occurred in the Microsoft .NET Framework while trying to load assembly id 65581”

After applying CU1, you need to execute:

dqsinstaller.exe -upgrade

This is typically from the folder C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn (but depends upon your installation path)

2012-04-27

Great to see our buddy Ola Hallengren has created an updated version of his database maintenance scripts. Many people use these in place of the database maintenance plans that ship with SQL Server.

Here’s the updated info from Ola and the best part is that they continue to be free:

New Version Available

A new version of the SQL Server Maintenance Solution is now available. The new version supports SQL Server 2012.

2012-04-22

Hi Folks,

For a while, I’ve been wanting to get some great SQL mugs printed for SQL Down Under but I need further inspiration so here’s your chance to get a collectors set of 5 SQL mugs:

Send me (greg @ sqldownunder . com) a great line to go onto the mugs, along with your country and a delivery address. I’ll pick the best 5 and get mugs printed with those sayings. If you’re one of the 5, I’ll send you a collectors set with one of each of the 5.

2012-04-14

I’ve been working on a team with Roger Doherty building parts of what’s now become the SQL Server 2012 Early Adoption Cook Book.

So, if you work on the bleeding edge of SQL Server and are keen to get your head around what’s coming, this is a seriously good resource.

Time to go and get it.

The material is constructed as a large number of bite-sized pieces. Each presentation is about 15 minutes in length, and each demo is about 5 minutes. And there are lots of them.

2012-02-02

Temp tables are visible within the scope where they are declared but also in sub-scopes. This means that you can declare a temp table in one stored procedure but access it in another stored procedure that is executed from within the first stored procedure.

There are two reasons that people do this. One reason is basically sloppy code, a bit like having all your variables global in a high level programming language. But the more appropriate reason is to avoid the overhead of moving large amounts of data around, and because we only have READONLY table valued parameters.

2012-01-05

We have a very common customer scenario where the customer decides to upgrade to a new version (in this case let’s say SQL Server 2012). They run upgrade advisor and note that there are a whole lot of problems. They think “Hey that’s way too much to deal with right now. I don’t have time”.

So they don’t deal with them. They upgrade the server to 2012 but leave their db_compat level at a lower level with the intention of dealing with the problems later.

2011-12-24

Well it’s been a while since I’ve posted up a new podcast. (I know, I know).

But I’ve just started a new series for SQL Server 2012. First out of the gate is Roger Doherty (Senior Program Manager in the SQL Server team) with an overview of all the key SQL Server 2012 pillars and enhancements.

You’ll find it here:

https://podcast.sqldownunder.com

Enjoy!

2011-12-21

Nice to see the increase in maximum database size on SQL Azure kicked up to 150GB.

In most enterprises I go into, there are a few databases that wouldn’t fit but now the vast majority of databases would fit in SQL Azure.

Also included in the November release are federations and an updated management portal.

More info here: http://msdn.microsoft.com/en-us/library/windowsazure/ff602419.aspx

2011-12-13

Over the years, I’ve seen several causes of this error in SQL Server Integration Services but today I came across another one.

You can get this error if you’ve used 3rd party components (particularly data sources) and the licensing for those components has expired.

Hope that helps someone sometime.

2011-12-13

When you first make a connection to the new LocalDB edition of SQL Server Express, the system files, etc. that are required for a new version are spun up. (The system files such as the master database files, etc. end up in

C:\\Users\\<username>\\AppData\\Local\\Microsoft\\Microsoft SQL Server Local DB\\Instances\\LocalDBApp1) 

That can take a while on a slower machine, so this means that the default connection timeout of 30 seconds (in most client libraries) could be exceeded.

2011-11-30