Viewing 15 posts - 1 through 15 (of 326 total)
Couldn't you check if the file exists In the destination folder first and if so move to unproccessed folder and then continue processing the next file?
I am not sure...
March 28, 2025 at 7:27 pm
Instead of moving processed files to a single archive folder, create a timestamped folder in the target folder and move the file there.
You will never get collisions if you...
March 28, 2025 at 7:25 pm
issue fixed. Adding IS_MS_SHIPPED = 0 removes the SP in question.
March 6, 2025 at 5:22 pm
I have made some progress on this. I had to change the FROM table and now I can see the creation and last modified dates. However, the query is showing...
March 6, 2025 at 5:12 pm
Does encrypting the DB cause performance issues (ie run time increases) for queries?
February 13, 2025 at 3:24 am
WITH ordered
AS (SELECT UNIT
,ORDER_DATE
,rn1 = ROW_NUMBER...
February 9, 2025 at 10:14 pm
You could change the approach to use a script task to execute your powershell script. However, if you can do this in PS - then you almost certainly can...
February 7, 2025 at 12:54 am
How are you specifying to run PowerShell, as a scripting task? Spitballing here, but could you run it as an Execute Process Task, with powershell.exe as the executable? Then...
February 6, 2025 at 6:12 am
I said 'add another THROW', not 'add another THROW 51000, '2. One or more stored procedures had errors, please investigate', 1;'!
Also, surely you want the INSERT to dbo.RunTimeErrors to...
February 3, 2025 at 8:46 pm
Did you add another THROW in the final CATCH block, like I suggested?
If yes, please post the code.
Yes I did. If I add the second THROW then the table...
February 3, 2025 at 5:49 pm
No, only 1 TV is required. You simply run multiple INSERTS to it in your code.
To make the error appear in the SSIS Output window, you need to add...
February 3, 2025 at 5:33 pm
Instead of logging your errors in a physical table (whose changes are being rolled back, I assume), log them in a table variable and then insert from the table...
February 3, 2025 at 4:23 pm
I swapped things around a bit. Obviously, I cannot test it.
ALTER PROCEDURE dbo.RunStoredProcedures
AS
SET NOCOUNT ON;
DECLARE @FAIL_COUNT INT = 0;
BEGIN TRANSACTION;
BEGIN TRY
BEGIN TRY
...
February 3, 2025 at 3:46 pm
I made some progress on this.
Code:
ALTER procedure [dbo].[RunStoredProcedures]
as
DECLARE @FAIL_COUNT INT = 0
BEGIN TRANSACTION
BEGIN TRY
BEGIN TRY
truncate table dbo.temptable
END TRY
BEGIN CATCH
SET @FAIL_COUNT = @FAIL_COUNT + 1
END CATCH
BEGIN...
February 3, 2025 at 5:29 am
I have been thinking more about this. I don't think relying on SSIS output window is the right way to capture errors. I need a persistent record of errors (not...
February 3, 2025 at 2:06 am
Viewing 15 posts - 1 through 15 (of 326 total)
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy