Grant Fritchey (7/30/2014)
Koen Verbeeck (7/30/2014)
Grant Fritchey (7/30/2014)
Koen Verbeeck (7/29/2014)
Grant Fritchey (7/29/2014)
As long as we're talking about straight T-SQL commands, you should be fine. If you start trying to access objects directly through SSIS, you may hit issues. Forward compatibility is not guaranteed like backward compatibility.How are you going to access objects directly? Through SMO?
No, I'm thinking about the SSIS objects that directly manipulate tables and may not expect certain data types. That sort of thing.
Your words are shrouded with mystere and riddles 😀
About which objects are we talking here? As far as I know there are no new data types in SQL 2014.
You're buying the next beer.
Not sure what I was thinking of, instead of data types, let's just say objects.
Does it work with in-memory tables if you link to them from 2012? I don't know, but I think it's worth asking.
Again, I never assume forward compatibility and I'm surprised that anyone would just blithely say it's fine. Not without extensive testing.
What? I bought the previous one! 🙂
As usual you are (partially) right. I tested it and you can read/write without issues to a clustered columnstore index, but the memory optimized table has one issue: if you want to write against it you have to disable the tablock option in the fast load options of the OLE DB destination.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP