Viewing 15 posts - 1 through 15 (of 23 total)
Brilliant! Problem solved.
Thank you
January 10, 2017 at 11:20 am
That's a good idea. Thanks for this.
November 4, 2016 at 12:58 pm
That was the problem- you nailed, Jacob Wilkins. I was updating the SP, but I wasn't actually executing it! What an amateur move.
It's been a few years since I...
October 21, 2016 at 2:45 pm
Shouldn't the statement --PRINT @cmd be irrelevant, seeing as how the code is commented out?
October 19, 2016 at 2:17 pm
I tried that, sure it would work, but for whatever reason, no records were added to the table. Here's the code I used:
ALTER PROCEDURE [dbo].[ImportJobRevenue]
@DataSourceJobRevenue AS varchar(100)
AS
SET...
October 19, 2016 at 2:07 pm
Sure. This is the entire code block in question:
USE [17-oct-2016_MainReport]
GO
/****** Object: StoredProcedure [dbo].[ImportJobRevenue] Script Date: 10/19/2016 11:26:06 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [dbo].[ImportJobRevenue]
...
October 19, 2016 at 1:07 pm
I was thinking it would be printed to the query window in which I'm running the SP, just above the message saying the command completed successfully.
I guess I have some...
October 19, 2016 at 1:04 pm
No, I am in a test environment.
October 19, 2016 at 12:49 pm
I gave this a shot, of course changing the database reference to match my DB name; but I got this error message:
Msg 137, Level 15, State 2, Line 4
Must declare...
October 19, 2016 at 12:49 pm
I had another idea that I really thought would work; but it isn't working, and I'm not sure why.
My idea was to simply add the code "Print @cmd" on the...
October 19, 2016 at 12:42 pm
Noted, for future threads.
Thanks again
October 19, 2016 at 12:16 pm
As it happens, I just got the restore this morning; so even if it wasn't the most efficient, server-load-friendly solution, it did do the trick.
However, I am going to keep...
October 19, 2016 at 12:05 pm
Unfortunately I'm using SQLExpress 2008, which apparently does not support SQL Agent.
I've noticed that part of the process that produces the value in the variable in question seems to be...
October 19, 2016 at 11:56 am
I thought of that, but when I ran the following code:
use MainReport
select object_name(m.object_id), m.*
from sys.sql_modules m
where m.definition like N'%ImportJobRevenue%'
to find all references to the proc in question...
October 17, 2016 at 4:51 pm
I think I will request the DB restore to a test server. That seems like the "easiest" thing to do.
Thanks, everybody, for the quick and thoughtful responses.
October 5, 2016 at 2:53 pm
Viewing 15 posts - 1 through 15 (of 23 total)