July 23, 2014 at 9:34 pm
Comments posted to this topic are about the item Exit Stage Right
July 24, 2014 at 2:14 am
Thank you dave, for the post, very good one.
I just went with eliminating the odds method and then I was stuck with 2 and 4, I read the deprecated features of 2012 (using local_help) and there was no hint of process failing, so I picked 4 by increasing the possibility of success rate... Bingo!!!.
...enjoyed the post.
later I came across this:
QUOTE
The staging process has changed since SQL Server 2008 R2. You can continue to use the SQL Server 2008 R2 process; however, the staging process is now more flexible and has better performance.
UNQUOTE
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
July 24, 2014 at 4:10 am
This was removed by the editor as SPAM
July 24, 2014 at 6:44 am
Raghavendra Mudugal (7/24/2014)
Thank you dave, for the post, very good one.I just went with eliminating the odds method and then I was stuck with 2 and 4, I read the deprecated features of 2012 (using local_help) and there was no hint of process failing, so I picked 4 by increasing the possibility of success rate... Bingo!!!.
...enjoyed the post.
later I came across this:
QUOTE
The staging process has changed since SQL Server 2008 R2. You can continue to use the SQL Server 2008 R2 process; however, the staging process is now more flexible and has better performance.
UNQUOTE
+1
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 25, 2014 at 10:02 am
Lots of head-scratching... Thanks, Dave!
July 25, 2014 at 11:01 am
I think that this is a pretty good question. But asking which answer is "most correct" is asking for a judgement call, rather than just for knowledge of a fact, so some people may claim it is not a good question - but DBAs and developers have to make judgement calls every day, so why shouldn't a QotD require one?
I picked the "they will still work" option over "they won't work because it has changed" because although neither is absolutely correct I believe that "it will work" will be true far more often than not. Why should I expect to create or delete collections in an MDS staging process? Surely once that has been done the process is staging the data as required, it shouldn't ever need to do that. Much the same applies to to reactivating deactivated collections and to reactivating deactivated members or adding members to or removing members from collections. So while some staging processes in SQL Server2008R2 may have done some of those things, and thus won't work in 2014, it's going to be much more common that the processes that need to be carried forward to the latest release don't do any of those things, so there's no reason they won't work.
Tom
July 26, 2014 at 3:18 am
I never used the SQL 2008R2 version of MDS (thank God), only the 2012 version. Got it right though.
Nice question.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 27, 2014 at 4:17 am
Interesting.
Thanks & Best Regards,
Hany Helmy
SQL Server Database Consultant
July 28, 2014 at 4:25 am
Thanks for question.
--rhythmk
------------------------------------------------------------------
To post your question use below link
https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply