Viewing 15 posts - 7,081 through 7,095 (of 59,072 total)
Step one is to remove all doubt. Do the SELECT COUNT(*) thing on the table.
You also say that you inserted millions of rows into the heap. There are a lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2020 at 1:55 pm
Disagreement noted.
However, there's nothing in what I stated that uses 24:00:00, nothing that would violate the constraint on the EndDate, and thee method I suggested actually does use the proper...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2020 at 1:41 pm
jonathan.crawford wrote:Jeff, quit torturing the poor guy and just give him the linkhttp://www.sqlservercentral.com/Forums/Topic530630-8-2.aspx
Nice. Is there a unicode version?
No, but the conversion should be fairly simple.
Man... I can't believe...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2020 at 1:10 am
Cool. Thanks Eric. I'll take a look.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 9:53 pm
Interesting. Does it correctly handle names like MacDonald, McDonald, van Halen, O'Leary, and things like "This is a Book"?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 7:29 pm
Focus on what tools can do for you instead of 12 year old reports of a tool's shortcomings.
Heh... I know what you mean. I've been saying the same thing...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 7:16 pm
...
It's funny how people think that you don't need xp_CmdShell on managed systems like Azure.
Do they also not allow for OPENROWSET()?
You can OPENROWSET (or BULK INSERT) from CSV,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 7:11 pm
Does the other "Initial Caps" function that you're talking about only hit the first letter of the entire string or is it more like "Title Caps"?
And this is what I...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 7:08 pm
p.s. You might want to also look into "Temporal Tables", which are a combination of Type 2 + Type 4 SCDs that do most of the work for you. All...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 6:20 pm
You don't actually need to store all rows that don't change to be able to do PIT (Point-in-Time) reporting. IMHO, it's actually foolish to do so because not only will...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2020 at 6:02 pm
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
Viewing 15 posts - 7,081 through 7,095 (of 59,072 total)