SQLSaturday Denmark precon registration is live

We’re proud to announce that the registration for precons at SQLSaturday Denmark is now live – we have managed to get some great speakers – and the topics they each talk about, are all really interesting and something that we all use or should use in our daily work with Business Intelligence and Microsoft SQL Server.precons-1024x543

Continue reading →

CU 4 for SQL Server 2014 ready

sql-server-2014It’s a good day today, the release of Cumulative Update 4 for SQL Server 2014 will fix a lot of¬†small and larger bugs.

Including the painfull one that task would shift to upper left corner in SSIS when resized.

Cumulative update package 4 for SQL Server 2014 (including update for SSIS) is available at http://support.microsoft.com/kb/2999197/en-us

This CU release contains a list of bug fixes for SQL in general, SSRS, SSAS and SSIS.

For SSIS fixes:

FIX: Tasks shift to upper-left corner when you move or resize them while designing a maintenance plan in SSMS 2014

FIX: Error in SQL task with IsQueryStoredProcedure set to True when you use .NET Data Provider for Teradata in SSIS

FIX: SSIS 2012 or SSIS 2014 XML Source task cannot load data from URI

For SSAS Fixes:

FIX: MDX query returns no result when the cache is not cleared after you run a previous query in OLAP or tabular model

FIX: User obtains incorrect data when two users in the same security role run a client report in SSAS 2012 or SSAS 2014

SQL Performance Fixes:

FIX: A severe error occurs when you run a query that uses CTEs against the partitioned tables in SQL Server

SSRS Fixes:

FIX: Error when you print, print preview, or export the report to PDF in SSRS 2012 or SSRS 2014

For the full list look here

SSIS Tip of the day

I’ve just learned a new tip about SSIS that I was not aware of. A tip that I think you all should know about,

When retrieving data via the OLE_DB connection, there are several options to how the data should be retreived. Often we just select “Table or View” option, mostly because we’re to lazy to write up the SQL that is needed for the operation.


Just be aware that when you do that, the SSIS engine will use the command OPENROWSET to get the data, but when you’re typing up the correct SQL to get the data and using the “SQL command” the SSIS engine will use the faster and more optimized SP_Executesql.