PeopleSoft Adoption Made Smooth & Simple!
On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool. Claim Your Free WalkMe Account Now
Course Of The Month
5 days, 13 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Compile-time conditions in stored proc?
Posted on 2013-06-05
I have some stored procs that reference a few linked servers in a distributed transaction. This works OK in live, but in my DR location I have fewer actual machines, and they contain databases that reside on separate machines in live.
Under the circumstances, i would have to use loop-back linked server names in DR, which would kill the distributed trans, or I would have to have two versions of the code - for DR and Live, that reference actual machine names - which pretty much defeats the purpose of disaster recovery.
I have tried solving the issue by adding conditions like
Is there a way of adding conditional statements that would be evaluated at "prepare" stage?
Or perhaps someone could suggest a different way of achieving what I am after?
Under the circumstances, i would have to use loop-back linked server names in DR, which would kill the distributed trans, or I would have to have two versions of the code - for DR and Live, that reference actual machine names - which pretty much defeats the purpose of disaster recovery.
I have tried solving the issue by adding conditions like
IF @@SERVERNAME = 'SQLPROD1' EXEC SQLPROD2.MyDB.dbo.mySP
ELSE EXEC SQLDR2.MyDB.dbo.mySP
Is there a way of adding conditional statements that would be evaluated at "prepare" stage?
Or perhaps someone could suggest a different way of achieving what I am after?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
2
5 Comments
Active 6 days ago
The fundamental problem you are facing here is that you are trying to solve applicatively an architecture problem. As a dirty hack you can eventually want to try something like this to fool the compiler (in pseudo code).
For creating linked servers applicatively, you can look at the following link:
http://msdn.microsoft.com/en-us/library/ms190479.aspx
Hope this helps.
if exists( linked server (SQLPROD2) or linked server (SQLDR2))
drop linked server SQLPROD2
drop linked server SQLDR2
IF @@SERVERNAME = 'SQLPROD1'
begin
create linked server SQLPROD2...
EXEC SQLPROD2.MyDB.dbo.mySP
drop linked server SQLPROD2...
end
ELSE
begin
create linked server SQLDR2...
EXEC SQLDR2.MyDB.dbo.mySP
drop linked server SQLDR2...
end
For creating linked servers applicatively, you can look at the following link:
http://msdn.microsoft.com/en-us/library/ms190479.aspx
Hope this helps.
I'm guessing you can get around this by using dynamic SQL:
DECLARE @SQL VARCHAR(max) = NULL;
IF (@@SERVERNAME = 'SQLPROD1')
BEGIN
SET @SQL='EXEC SQLPROD2.MyDB.dbo.mySP';
EXEC @SQL;
END
ELSE
BEGIN
SET @SQL='EXEC SQLDR2.MyDB.dbo.mySP'
EXEC @SQL;
END
Active 6 days ago
<<I'm guessing you can get around this by using dynamic SQL:>>
Definitely a more elegant solution. You just me realize I have a bias onto not mixing up dynamic SQL and multi server distributed transactions for security purposes and error feed backing reasons. Thanks (I do mean it) :)
Definitely a more elegant solution. You just me realize I have a bias onto not mixing up dynamic SQL and multi server distributed transactions for security purposes and error feed backing reasons. Thanks (I do mean it) :)
Both viable ideas, guys. thanks... I have to say that dropping and recreating linked servers sounds a bit clumsy to me, though, and dynamic SQL introduces its own complications because my stored procs have output parameters. Besides, isn't there a performance hit with dynamic SQL because it has to re-generate the execution plan? Or is that a moot point, because SPs (and their execution plans) are atomic, anyway, even when sub-called?
Actually, there is yet another complication to this - I also have a QA environment where server names are yet again different, but there I also have the added complication of database names being different (MyDB_QA1, MyDB_QA2, MyDB_Dev, etc) I do not think that problem can be resolved by architectural changes, as originally pointed out - I have to have these multiple copies of the databases. I guess I will have to go the dynamic SQL route... Thanks again.
Actually, there is yet another complication to this - I also have a QA environment where server names are yet again different, but there I also have the added complication of database names being different (MyDB_QA1, MyDB_QA2, MyDB_Dev, etc) I do not think that problem can be resolved by architectural changes, as originally pointed out - I have to have these multiple copies of the databases. I guess I will have to go the dynamic SQL route... Thanks again.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
International Data Corporation (IDC) prognosticates that before the current the year gets over disbursing on IT framework products to be sent in cloud environs will be $37.1B.
In this article we will learn how to fix “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.
Suggested Courses
Course of the Month5 days, 13 hours left to enroll
707 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.