Viewing 15 posts - 8,896 through 8,910 (of 59,099 total)
BWAAAA-HAAAA-HAAAAA!!! "Modern"? It may be more recent but it sure as hell isn't more "Modern". "Crippled" is a much better word!
Technically, the given answer is incorrect because you can, indeed,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2019 at 2:04 pm
Hi Jeff,
Below is the index that key lookup is using. Can you please let me know how I can use COUNT with a GROUP BY that matches the keys...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2019 at 6:18 pm
Thank you for the feedback, folks. It'll be interesting to find out if anyone uses it for the things that I've started to use it for or maybe even a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2019 at 6:07 pm
The code I showed was missing and "end" and a ")".
But was suggested to me that I would use this instead, and it works great!
In case someone else...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2019 at 2:34 pm
I am using Visual studio to design databases for applications / data warehousing rather than just using the SSMS designer like I did in the past, but now I...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2019 at 2:31 pm
Hi,
I'm seeing key lookup which is taking 95% of time for a query. I have verified and made sure that there is no index fragmentation and stats are up...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2019 at 2:20 pm
There's actually a very easy, almost trivial method to solve this problem. Here's the article on how you could pull this off. And, please, tell us why they want to...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2019 at 1:51 pm
Sounds more like a bug than a feature. Is this actually useful for anything beyond bar bets? Why would a single insert that breaks the rules be advantageous? Especially...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2019 at 1:14 pm
Totally agreed on that, Jason! It'll be interesting to see if anyone posts theirs. And, thank you for posting yours!
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2019 at 9:59 pm
Thanks for the very kind feedback, Jason.
Interesting code, Jason. While I've seen such a thing before, I've not seen many folks that provide a starting value and number of rows...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2019 at 5:41 pm
When the infrastructure team patches windows server and reboots, I would like to have a solid checklist of things which should be done to say 'sql server and databases...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2019 at 4:45 pm
And use try..catch
I hear a whole lot of people making that recommendation. Try/Catch is usually not necessary, especially in the presence of SET XACT_ABORT ON, which will auto-magically produce...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2019 at 4:21 pm
No, Jeff, an identifier is by its very nature measured on a nominal scale. It is not an interval scale. It is not a ratio scale. It is not...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2019 at 2:54 pm
Jeff,
I spent the last 2 days or so on the first article. I got about half way through. I think I understand the concept. One part I couldn't figure...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2019 at 2:09 pm
In doing further (and better) research on this today when it happened, the head blockers are executing a stored procedure that updates a table.
If it's a joined update, please...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2019 at 8:03 pm
Viewing 15 posts - 8,896 through 8,910 (of 59,099 total)