Viewing 15 posts - 9,061 through 9,075 (of 59,091 total)
I've been accepted to speak at Providence, RI this year. I'm presenting "Black Arts" Index Maintenance parts 1 & 2.
https://www.sqlsaturday.com/892/Sessions/Schedule.aspx
As a bit of a side bar, it'll be interesting...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2019 at 3:22 pm
Thank you all for the responses. I am a big supporter of staying within the MS stack and taking the natural migration to Azure, but there is a major...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2019 at 2:30 pm
The only exception is for daily transfer of 40GB in 140 KISAM files from a third party system and found SSIS the fastest method.
I don't know what a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2019 at 2:14 pm
I've been working with a young developer for over a year on trying to get her to format any SQL she writes, SSIS or SSRS packages. Since I...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2019 at 7:12 pm
I don't trust anyone... not even myself! 🙂
My name is Grant Fritchey and I endorse this message. Except I'd change it slightly: I don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2019 at 7:08 pm
whereas a move to Talend would allow non-developer staff to handle integration task more easily due to it's drag and drop interface.
THAT RIGHT THERE is a very strong reason...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2019 at 3:28 pm
p.s. Venting is good... being old, I can tell you, it keeps you from farting so much. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2019 at 3:17 pm
I've been working with a young developer for over a year on trying to get her to format any SQL she writes, SSIS or SSRS packages. Since I do...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2019 at 3:16 pm
Don’t make me post some examples. The issue isn’t so much the implicit join but rather understanding the criteria in the WHERE statement when it contains the join information...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2019 at 2:03 am
I don't trust anyone... not even myself! 🙂
My name is Grant Fritchey and I endorse this message. Except I'd change it slightly: I don't trust anyone......
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2019 at 1:56 am
Lordy. I, unfortunately, found what I was looking for at item #12 at the following URL...
... which states...
Disable antivirus software from scanning FILESTREAM volumes if it's not mandatory within...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2019 at 1:18 am
Never mind... I looked it up. It would appear that if you allow it, the files become a part of the backups... basically, using SQL Server to backup part of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2019 at 11:58 pm
My experience with, and knowledge, filestream is somewhat limited, so I'm hesitant to pronounce too strongly on this approach. I do know that files within databases leads to all...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2019 at 11:41 pm
Young man (or woman), Implicit joins are evil. Always. Even in examples or practice exercises. Repent of your wicked ways.
BWAAA-HAAAA!!!!! Someone needs to tell MS that. Properly written correlated...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2019 at 11:28 pm
A minor point I came across today - your "favourite way" to produce the Tally table does not work in an Azure database:
SELECT TOP 11000 --equates...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2019 at 11:11 pm
Viewing 15 posts - 9,061 through 9,075 (of 59,091 total)