Viewing 15 posts - 31 through 45 (of 155 total)
Thank you very much for your responses.
Would you happen to know which system variable shows which proc executed? That is the main issue.
The are no problems, only solutions. --John Lennon
January 18, 2024 at 6:21 pm
Options are the Try-Catch block at the end of the procs. Although this is really inefficient, it follows the original design of the ETL job. I think consistency is important...
The are no problems, only solutions. --John Lennon
January 11, 2024 at 3:47 pm
Hi Phil,
Nice to see you and Happy New Year!
You are correct. The ETL is set up to continue on failure due to the amount of data that is being processed....
The are no problems, only solutions. --John Lennon
January 11, 2024 at 3:02 pm
Thank you Scott!!
This is exactly what I need.
The are no problems, only solutions. --John Lennon
October 20, 2022 at 7:39 pm
Fredrico,
Are you suggesting searching in Management Studio or Visual Studio. I am not sure if I have searched the way you are suggesting.
Thank you so much for your response!
Dave
The are no problems, only solutions. --John Lennon
October 20, 2022 at 7:37 pm
Thank you for your response, but I am looking for a query that searches all stored procedures for the '##' sign. I can't manually check all of them we have...
The are no problems, only solutions. --John Lennon
October 20, 2022 at 6:31 pm
Awesome! Thank you soooo much for that explanation. I was half right 🙂
The are no problems, only solutions. --John Lennon
July 13, 2022 at 5:25 pm
Hello SSC,
This issue has been resolved, but it had nothing to do with the excel version. There was a step in the SSIS package that was renaming the excel file...
The are no problems, only solutions. --John Lennon
December 13, 2021 at 8:59 pm
Hi Phil,
Nice to hear from you. I will try this. I hope you have a great holiday and stay safe!
The are no problems, only solutions. --John Lennon
December 9, 2021 at 3:33 pm
250 is a lot for a fact table. I had a dimension table that had 573 columns. The problems encountered were during updates due to page splits. So...
The are no problems, only solutions. --John Lennon
May 10, 2021 at 1:07 pm
250 seems like a lot of facts! Are you happy that you've got the data modelling correct?
Not sure I understand what you are saying Phil.
The are no problems, only solutions. --John Lennon
May 10, 2021 at 1:03 pm
Ok, good point, we want to make sure that other developers have correct info. I gave the answer to Jeff. Please let me know if it's accurate.
This answers my question....
The are no problems, only solutions. --John Lennon
April 8, 2021 at 2:44 pm
Thank you all very much for your responses! Mystery solved 🙂
Stay safe folks!
The are no problems, only solutions. --John Lennon
April 8, 2021 at 12:54 pm
Thank you very much for clearing this up, Michael. Also, thank you to everyone on SSC who commented! I really, really appreciate it! This was very educational for me.
I will...
The are no problems, only solutions. --John Lennon
January 18, 2021 at 5:32 pm
Thanks Voldemar. I'll save that query. I have researched DMV's, Query store and Data Collector, but my issue is that I am all theory when it comes to CPU, I/O,...
The are no problems, only solutions. --John Lennon
January 17, 2021 at 11:26 pm
Viewing 15 posts - 31 through 45 (of 155 total)