I'll be there! Attending SQL 2014 pre-con on Thu and all day Fri. Sadly have to miss the Saturday for a wedding - how inconsiderate!

There are a number of problems with that piece of code (and this is just what I can see via my phone):

- the date parameters are not used in...

Hmm I still can't quite tell (I'm away from keyboard this week an only have phone!). The two LEFT JOINs might be an issue, remove them one by one...

As I can't see your data, it's hard to tell where the duplicates are coming in. Can you post an example of the duplicate data? Anonymise your actual...

Well you can change the column definition in the #contacts temp table to allow NULLs, but this does again question your data quality.

The main problem with this proc is that you reference the CTE twice. SQL Server will process that twice because CTEs behave like views rather than temp tables. ...

Just to state the obvious, but have you deployed the Attunity connectors on the Win 2008 box?

We have these working in our environment but I do remember it being a...

If the OP has just restored the database from SQL 2008 R2 to SQL 2014, then the compatibility mode (and therefore cardinality estimation model) will remain as 100, ie the...

You can do what you describe, it's called Composable DML. This is much more powerful with the MERGE statement where you can access columns from the inner MERGE which...

First of all, try it. Have you got an MSDN subscription? Or make use of the free trial. You have spin up a trial SQL Server 2014...

Superstitious, anecdotal reasons for not upgrading, OR known workload, trialled extensively on comparable proof-of-concept kit? Hide until 2017, OR clearly attempt to identify positives and negatives. Specific tests...

I think this query would be a lot easier if you had a normalized table structure ( FY, ObjSub, Dept, Period, Value ) and a calendar table, but if that...

OK scaled up my Azure VM to 8 core / 14GB and the rows to 50 million. Created similar(ish) test rigs for: normal table, columnstore, in-memory OLTP table and...

See my reply here on a similar issue:

http://www.sqlservercentral.com/Forums/Topic1557258-3411-2.aspx

I did find some evidence that an index hint on a range index running in a natively compiled proc was the quickest, but results seemed a bit variable. For...