Viewing 15 posts - 7,126 through 7,140 (of 59,102 total)
Thanks for your feedback. Much appreciated.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 2:54 pm
To answer the question, I like the first one better because the first CTE DRYs out some of the formulas. It doesn't make much difference here but, when you have...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 2:43 pm
Try this
SELECT v.n2.value('(@*:ObjectName)[1]','varchar(30)') AS Name,
p.n1.value('(@*:ObjectName)[1]','varchar(30)') AS Scope
FROM #SSISTest st
CROSS APPLY st.PackageXML.nodes('//*:Executable') AS p(n1)
CROSS APPLY p.n1.nodes('*:Variables/*:Variable') as v(n2);
Man... I remember you helping me with...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 2:12 pm
Azure SQL is still 99% the same familiar T-SQL we've been using for decades. Some features like Availability Groups and DBCC commands are gone, because they have been replaced...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 2:08 pm
Just my dip of the toe into the problem. I have this thing for making my dynamic SQL look the same as static SQL. I also used a little trick...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 5:38 am
p.s. I'm probably a minority here but I hate the look of StackOverflow and similar sites. Everyone has gone that way to support mobile (i.e. smart phones) and so don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2020 at 8:20 pm
Understood on not changing the data in the existing column. It could really screw up a lot of code that's depending on the bloody NULLs.
If you can add a persisted...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2020 at 8:13 pm
thx for the suggestin Jeff. I'd really prefer NOT to free the cache.. Looking for the command to mark the procs for RECOMPILE -- across all DB's..
Like Jeffrey Williams...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2020 at 7:53 pm
Correct... it doesn't look much different. It's when you try to use the forum and related functionality. Their stuff works better than ours do. Sometimes, ours doesn't work at all.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2020 at 4:35 pm
From my personal observations, "OR" in criteria is more often a problem than not and, with that, I tell people to make their EndDate column NOT NULL and have it...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2020 at 4:24 pm
Here's a simplification of Jonas' method above.
--===== Create the test table and populate it.
-- This is NOT a part of the solution.
DECLARE...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2020 at 4:06 pm
That show at the end is absolutely awesome. Thanks, Steve.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2020 at 2:42 pm
DBCC FREEPROCCACHE;
Understand that there could be a period of some pretty high activity and some slowness until all the procs being used are recompiled on their first runs.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2020 at 1:55 pm
BrainDonor beat me to the link he provided. I'll also add that if you're having serious problems with TempDB, there's usually some code in desperate need of a fix.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2020 at 1:53 pm
Thanks for the info and link.
It looks like the on-premise DBA is going to be met with a few challenges in the future. I know there are a lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 13, 2020 at 1:14 pm
Viewing 15 posts - 7,126 through 7,140 (of 59,102 total)