Viewing 15 posts - 6,451 through 6,465 (of 59,091 total)
Sorry, it wasn't directed at you. It was a post I commented on when it first came out and...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2020 at 7:26 pm
As general issues go does this require ##temp to have global scope? Also, why make the variables varchar(max)? I got it to work like this
drop table...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2020 at 3:56 pm
My recommendation is that you, if you're using them, that you forget you ever saw "incremental rCTEs" regardless of the number of rows involved. Please see the following article for...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2020 at 3:52 pm
Why not just use a SEQUENCE?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2020 at 1:49 pm
That's nothing.
How about 2 multi-million rows tables (one of them is closer to billion) joined by a value extracted from an XML column?
Yes, by XML_col.value('XML path', 'int' )
The job...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2020 at 1:36 pm
Did you ever figure out what your backup problem was and how to fix it?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2020 at 12:26 am
Ok... I have a question, especially seems to be coming up a lot lately.
To what end does someone need this type of information? What will the information ultimately be...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2020 at 12:22 am
thanks for highlighting the issue. i have fixed the code.
updated code available in below link.
Please post the code on this site, Ram... the content of pastebin could simply vanish...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2020 at 11:38 pm
I'm assuming that your tables are NOT named T01. T02, T03, etc and so I'm asking the following question again...
Is there a pattern to the actual name of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2020 at 8:54 pm
Still there is a shorter version:
select *
from leftTable T1
join rightTable T2
on (
T1.C1...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2020 at 8:47 pm
Hi,
I'm have sysadmin rights but it is not possible for me to delete auto created statisitcs. I receive the message, that the statistic doesn't exits or I do not...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2020 at 8:44 pm
Just in case you're not been able to find the reference for the formats...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2020 at 8:39 pm
Heh... to Sergiy's point, I wonder how many supposed "Big Data" problems are actually BIG "poor design", "poor implementation", "poor requirements", and "poor coding" problems. To wit, my definition of...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2020 at 7:54 pm
Thanks Jeff and Sergiy for all your help.
I have a much better understanding now and have some design ideas: instead of triggers, partitioned views I can use not just...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2020 at 7:40 pm
It would probably help your cause a bit if you posted what several good and bad rows actually look like.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2020 at 7:38 pm
Viewing 15 posts - 6,451 through 6,465 (of 59,091 total)