Viewing 15 posts - 20,401 through 20,415 (of 59,072 total)
Duran (6/10/2015)
Hi Jeff,Thanks for the reply, you mentioned that it depended on a couple of things, in a nutshell, what are those things?
Regards,
D.
Pretty much what I said in my previous...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2015 at 8:03 am
Tom_Sacramento (6/10/2015)
The primary key is a GUID called ID - not my idea, but this is an inherited database...
What I need is a count of each of the 3...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2015 at 7:39 am
PatrickSimons (6/10/2015)
Jeff Moden (6/9/2015)
PatrickSimons (6/9/2015)
I agree 100%. Especially when you SELECT INTO inside a transaction to a temporary table (##) = worst case....
What problems have you had there? Or...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2015 at 7:37 am
r.e.kiser (6/10/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2015 at 7:33 am
David Burrows (6/10/2015)
Jeff Moden (6/9/2015)
Is the number of columns in the final output a given or do we have to have the code figure that out?
Shouldn't that be max number...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2015 at 7:22 am
ericpap (6/8/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2015 at 12:45 am
I know it doesn't help except that misery loves company. I've never seen a new revision of SQL Server where there weren't some horrible slowdowns even if you did...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2015 at 12:41 am
I have to ask the question, please. Why is there a need to replicate a table to the same database? What is the reason?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2015 at 12:38 am
ramya.sqlservr (6/9/2015)
Jeff Moden (6/9/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2015 at 11:35 pm
BTW, if anyone wants some official MS documentation on the subject, please see the following article.
FIX: SELECT INTO Locking Behavior
Also notice the line where it says that this isn't a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2015 at 11:32 pm
PatrickSimons (6/9/2015)
I agree 100%. Especially when you SELECT INTO inside a transaction to a temporary table (##) = worst case....
What problems have you had there? Or are you citing...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2015 at 10:29 pm
Thordog (6/9/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2015 at 10:26 pm
It depends on a couple of things but, generally speaking and considering the size of today's databases, auto incrementing by 1MB is a horrible thing to do especially with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2015 at 10:17 pm
I have to say that this is one of the weirdest set of answers I've ever seen. This is the reason why I don't take certification tests. 😛
I...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2015 at 10:12 pm
Despite the whacko delimiters, importing this will be a breeze (looks like the ol' AT&T junk I used to have to load from tape). You just can't use (IIRC)...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 9, 2015 at 9:57 pm
Viewing 15 posts - 20,401 through 20,415 (of 59,072 total)