1,105,295 Community Members

Looking for work-around

Member Avatar
pritaeas
mod_pritaeas
11,285 posts since Jul 2006
Reputation Points: 1,420 [?]
Q&As Helped to Solve: 1,829 [?]
Skill Endorsements: 154 [?]
Moderator
Featured
Sponsor
 
0
 

I want to have the following on SQL Azure:

IF EXISTS(SELECT * FROM [sys].[databases] WHERE [name] = db_name() AND [compatibility_level] = 110)
BEGIN
    ALTER PROCEDURE [dbo].[Test] AS 
    BEGIN 
        -- Omitted body containing lots of strings
    END
END

or a work-around that does something similar. What follows is what I'm trying to avoid:

IF EXISTS(SELECT * FROM [sys].[databases] WHERE [name] = db_name() AND [compatibility_level] = 110)
BEGIN
    EXEC [sys].[sp_executesql] N'ALTER PROCEDURE [dbo].[Test] AS 
    BEGIN 
        -- Omitted body containing lots of strings
    END'
END

The reason I want to avoid the above, is because the stored procedure contains a lot of strings that need escaping.

LastMitch
Deleted Member
 
0
 

@pritaeas

Looking for work-around

What do you mean by work around? I never heard work around. I know you are using SQL Azure.

You can try Start a Job or Stop a Job:

This is for stop a job:

CREATE PROCEDURE [sys].[StopJob](@id)
AS
UPDATE [databases]
WHERE [name] = db_name()
AND [compatibility_level] = 110

ALTER PROCEDURE [dbo].[Test]
AS
BEGIN 
Member Avatar
pritaeas
mod_pritaeas
11,285 posts since Jul 2006
Reputation Points: 1,420 [?]
Q&As Helped to Solve: 1,829 [?]
Skill Endorsements: 154 [?]
Moderator
Featured
Sponsor
 
0
 

I'm not sure what you are getting at. My problem is just that the 1st SQL shown doesn't work, and I am looking for something other than the 2nd. I don't see any relation to jobs.

You
This article has been dead for over three months: Start a new discussion instead
Post:
Start New Discussion
View similar articles that have also been tagged: