Viewing 15 posts - 8,896 through 8,910 (of 59,091 total)
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
in VS - yes we can use the variables to replace with the appropriate database name - This can be done on the synonyms so we can still avoid...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2019 at 7:49 pm
From the Article:
Triggers are not allowed in our production environment...
Heh... I realize that a lot of folks abuse triggers and write horrible trigger code but flat outlawing such an incredibly...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2019 at 5:24 pm
I take it you never need to make copies of prod then or, perhaps, you use the same method to make such copies? There's just no way that I'd allow...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2019 at 3:33 pm
For ad hoc stuff, I don't use a programmatic method to commit or rollback. Someone at one of the companies I used to work for did such a thing. There...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2019 at 3:29 pm
Are we talking about front end code or stored procedures here? And, please pardon my ignorance of VS. I've never actually used it.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2019 at 2:19 pm
I haven't used the MERGE statement since I got burned many years ago doing a
WHEN NOT MATCHED BY SOURCE THEN DELETE
As it turns out, you end...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2019 at 2:04 pm
We once used to utilizing them, but with the advent of database projects in VS, we abandoned them again from our development. This due to the reason, that VS...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2019 at 2:00 pm
Synonyms can be useful for whomever created them, but confusing for others who stumble across them by accident. It depends on the purpose, but I prefer views instead.
Interesting. I've...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2019 at 1:58 pm
Viewing 15 posts - 8,896 through 8,910 (of 59,091 total)