Viewing 15 posts - 6,091 through 6,105 (of 59,098 total)
Yes... the deprecated types should be changed to the modern types... or at least according to MS. So here's how to fix some of the mistakes MS made when creating...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2020 at 3:40 am
First, nothing has been attached that I can see.
Second, if you did this without the understanding that now all the stuff that might fit "in-row" is now "in-row", which greatly...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2020 at 8:22 pm
SQL can only backup to drives which are local to the SQL server not remote drives unless you use UNC paths etc to provide backups to network locations.
IIRC, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2020 at 8:12 pm
Personally, I don't care for the use of HierarchyID nor it's particular form of positional notation. It's also a bugger to fix if something goes wrong with it.
Perhaps the following...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2020 at 7:44 pm
To be sure, you don't need to rebuild ALL indexes... just the ones that became seriously fragmented because of the index-inversion the shrink.
I also recommend temporarily moving your largest indexes...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2020 at 4:44 pm
WHERE
D >= DATEADD(MINUTE, DATEDIFF(MINUTE, 0, GETDATE()) / 15 * 15, 0) AND
D < DATEADD(MINUTE, DATEDIFF(MINUTE, 0,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2020 at 2:52 am
it worked thank you!
What was it that worked for you?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 19, 2020 at 2:15 am
...send reminder text messages...
You need to figure out a couple of things before you go off half-cocked doing something like that. People need to "opt-in" and be informed that...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2020 at 7:33 pm
no matter whether you like it or not, 1)application developers write managed code more; 2)application developers implemented the functions, including FORMAT, CONVERT, CAST, LTRIM, RTRIM, TRIM, LEFT, RIGHT; 3)FORMAT...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2020 at 3:37 pm
I really hope this isn't a dumb question. Is there a reason other then style or preference as to why you'd do this:
IF @Var1...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2020 at 2:22 pm
Phil, I don't understand why you think you need the self-join in your code.
It's simple, really: I never seem able to remember that you can update a CTE directly!
😀
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2020 at 4:46 am
I think the default should be that you're automatically "opted out" unless you decide to "opt in". Of course, that won't be profitable for these vendors and so that will...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2020 at 4:37 am
true, format() is slower, and I started using it since it was not available until SQL server 2012 and my employer migrated from SQL 2008 to SQL 2016. Just...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2020 at 4:23 am
Phil, I don't understand why you think you need the self-join in your code. It can still be done in a single scan of the table.
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 16, 2020 at 7:20 pm
I'm afraid that ROW_NUMBER() isn't going to hack it for this problem, Phil. Here's what the output of your code is...
EDIT: My...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 16, 2020 at 7:15 pm
Viewing 15 posts - 6,091 through 6,105 (of 59,098 total)