Viewing 15 posts - 16,636 through 16,650 (of 59,101 total)
PearlJammer1 (10/17/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 6:31 pm
Alaster07 (10/14/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 11:12 am
Beatrix Kiddo (10/17/2016)
sqladdict (10/17/2016)
They better not deprecate SSMS! Visual Studio just won't cut it.
Agreed!
If they ever did retire it, so would I. Retire, that is. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 9:44 am
hegdesuchi (10/17/2016)
thank you very much!How can i achieve that using except clause?
EXCEPT will only produce a list of rows that aren't the same. Sure, it's a good start but...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 9:31 am
drew.allen (10/17/2016)
Your client doesn't know what he is talking about
Careful now... if there are column-based audit or alert triggers on the table, then the client DOES know what they're talking...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 9:23 am
Was the TR and CDC in place for a good period of time before the large DIF problem occurred?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 9:18 am
Iulian -207023 (10/17/2016)
Jeff Moden (10/17/2016)
My answer would be "None of the above" because I don't want people to store XML in the database. 😉
Well ... there is also the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 9:15 am
My answer would be "None of the above" because I don't want people to store XML in the database. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 8:55 am
yo.mawtin (10/17/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 8:44 am
aaron.reese (10/17/2016)
When you do code-first design
Heh... "Never". 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 8:42 am
Phil Parkin (10/17/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 8:03 am
Eric M Russell (10/17/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 7:50 am
PearlJammer1 (10/17/2016)
It is because we have a situation where some tables appear to have id values less than the current identity value which will get auto generated on next...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 7:40 am
It's a bloody shame that any of them work. It's just another thing for people to mess up things with, just like many folks already do with sub-queries in...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 12:03 am
sqladdict (10/14/2016)
So Annoying. Please up vote to get this fixed.
Ships passing in the night... It was marked as "FIXED" an hour before you posted. 😉 It'll be in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2016 at 11:34 pm
Viewing 15 posts - 16,636 through 16,650 (of 59,101 total)