Viewing 15 posts - 8,056 through 8,070 (of 59,072 total)
That's certainly another viable option and it has kind of a user interface built in.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2019 at 4:24 pm
Yes, partially (although it almost never hurts to do so). It may also be an indication that you have code to fix that might still blow through whatever memory you...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2019 at 4:19 pm
I think it's actually a much more valuable skill to learn when to NOT change. I've seen a lot of so called "improvements" to things, especially in the world of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2019 at 4:09 pm
It's not bad enough that some of us have problems with the likes of using the wrong kind of rounding or what have you. SQL Server "helps" us make some...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2019 at 3:07 pm
On the subject of the tired adage of "Good/Fast/Cheap... Pick 2.", I end up saying to people that tell me that, "Ummmm... Ok... I thought you were a professional". 😉
There's...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2019 at 2:42 pm
Just be mindful of the possible surprise such a change could cause if the departure data has a midnight time.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2019 at 10:19 pm
How about some nice triangular joins done inside a cursor? Jeff Moden: Look Away.
Oddly enough, I was going to suggest Triangular Joins. I decided not to because I don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2019 at 10:16 pm
Thanks all - I thought there might just be some super simple reason like PIVOT just works better with in-memory data etc.
There might be!!! Did you try what I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2019 at 3:03 pm
Hi John, thanks for the reminder about SQL injection. I think we are ok in this case.
Despite your thoughts, you're still concatenating the table name without checking to see...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2019 at 2:58 pm
The KB was released due to an error in the RTM edition of SQL Server 2019.
Like I said in a different post, new versions of SQL Server scare...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2019 at 2:39 pm
If you wanted to be absolutely sure, you could change what is captured in the error log to log both successful and unsuccessful logins and then bounce the service to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2019 at 2:17 pm
Awesome! Looking forward to seeing it, John!
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2019 at 2:10 pm
What do you get when you write it with straight criteria instead of selecting from the sub-query?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2019 at 1:51 pm
Of course, that recommendation also comes with the warning that if the hashbytes are different, then the rows are guaranteed to be different. However (and you know this...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2019 at 1:42 pm
SELECT CONCAT('
SELECT ''', QUOTENAME(t.TABLE_SCHEMA), '.', QUOTENAME(t.TABLE_NAME), ''' [TABLE_NAME], COUNT(*) COUNT
FROM (SELECT ',x.c, '
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2019 at 11:22 pm
Viewing 15 posts - 8,056 through 8,070 (of 59,072 total)