tags:

views:

282

answers:

3

Set database name dynamically in SQL SErver Stored procedure?

+5  A: 

Stored Procedures are database specific. If you want to access data from another database dynamically, you are going to have to create dynamic SQL and execute it.

Declare @strSQL VarChar (MAX)
Declare @DatabaseNameParameter VarChar (100) = 'MyOtherDB'

SET @strSQL = 'SELECT * FROM ' + @DatabaseNameParameter + '.Schema.TableName'

You can use if clauses to set the @DatabaseNameParameter to the DB of your liking.

Execute the statement to get your results.

Raj More
Just beware that there are a lot of limitations to this approach. For example, the dynamic SQL is in a completely different scope, so it doesn't have access to table variables, temporary tables, etc. that are in your stored procedure. Also, there are big potential security issues with it. You should check out http://www.sommarskog.se/dynamic_sql.html before using this approach.
Tom H.
+2  A: 

This is not dynamic SQL and works for stored procs

Declare @ThreePartName varchar (1000)
Declare @DatabaseNameParameter varchar (100)

SET @DatabaseNameParameter = 'MyOtherDB'

SET @ThreePartName = @DatabaseNameParameter + '.Schema.MyOtherSP'

EXEC @ThreePartName @p1, @p2...   --Look! No brackets
gbn
+2  A: 

Sometimes, the use of SYNONYMs is a good strategy:

CREATE SYNONYM [schema.]name FOR [linkedserver.][database.][schema.]name

Then, refer to the object by its synonym in your stored procedure.

Altering where the synonym points IS a matter of dynamic SQL, but then your main stored procedures can be totally dynamic SQL-free. Create a table to manage all the objects you need to reference, and a stored procedure that switches all the desired synonyms to the right context.

This functionality is only available in SQL Server 2005 and up.

This method will NOT be suitable for frequent switching or for situations where different connections need to use different databases. I use it for a database that occasionally moves around between servers (it can run in the prod database or on the replication database and they have different names). After restoring the database to its new home, I run my switcheroo SP on it and everything is working in about 8 seconds.

Emtucifor