Solved

EXECUTE cannot be used as a source when inserting into a table variable.

Posted on 2010-11-16
11
532 Views
Last Modified: 2012-05-10
the following format works in 2005, not in 2000...

what would be the equivalent of the same in 2000?
insert @test
EXEC ('EXEC ' + @database_name + '.dbo.sp_helprotect')

*@test is a table variable
*@database_name is a temp variable
0
Comment
Question by:anushahanna
  • 4
  • 4
  • 3
11 Comments
 
LVL 60

Expert Comment

by:chapmandew
ID: 34147907
Yep, you can't do that in 2005.  2008 you can I believe, but not 2005.  Use temp tables instead.
0
 
LVL 6

Author Comment

by:anushahanna
ID: 34147972
no, i meant to say
insert @test
EXEC ('EXEC ' + @database_name + '.dbo.sp_helprotect')

works in 2005, not in 2000.

how would you do it in 2000?
0
 
LVL 58

Expert Comment

by:cyberkiwi
ID: 34147984
Just a sql server 2000 limitation.
#Temp works, so a 2-step process will work

if object_id('tempdb..#test') is not null drop table #test;
declare @database_name varchaR(100) set @database_name = 'tempdb'
declare @test table (owner sysname, object sysname, grantee sysname, grantor sysname, protecttype sysname, action sysname, [column] varchar(1000))
create table #test (owner sysname, object sysname, grantee sysname, grantor sysname, protecttype sysname, action sysname, [column] varchar(1000))
insert #test
EXEC master.dbo.sp_helprotect
insert @test select * from #test
select * from @test
0
Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

 
LVL 6

Author Comment

by:anushahanna
ID: 34147989
in other words,
EXEC ('EXEC ' + @database_name + '.dbo.sp_helprotect') would work wtih regardless of temp table or table variable.. in 2005..

is there a way to do it in one sentence like that in 2000...
0
 
LVL 60

Expert Comment

by:chapmandew
ID: 34147991
I'd use temp tables.  :)
0
 
LVL 58

Expert Comment

by:cyberkiwi
ID: 34147997
Sorry, was testing, this is the complete one including your @database_name variable

if object_id('tempdb..#test') is not null drop table #test;
declare @database_name varchaR(100) set @database_name = 'master'
declare @test table (owner sysname, object sysname, grantee sysname, grantor sysname, protecttype sysname, action sysname, [column] varchar(1000))
create table #test (owner sysname, object sysname, grantee sysname, grantor sysname, protecttype sysname, action sysname, [column] varchar(1000))
declare @sql varchar(1000)
set @sql = 'insert #test EXEC [' + @database_name +'].dbo.sp_helprotect'
exec(@sql)
insert @test select * from #test
select * from @test
0
 
LVL 58

Expert Comment

by:cyberkiwi
ID: 34148007
> I'd use temp tables.  :)

Yes, so would I.. haha
0
 
LVL 6

Author Comment

by:anushahanna
ID: 34148035
Oh-- perfect..

so there are 2 limitations, actually?

the exec within the exec part...
and
table variable, too, right?
0
 
LVL 58

Accepted Solution

by:
cyberkiwi earned 380 total points
ID: 34148066
There is only one - the table variable
I was iterating through options, and removed the double EXEC while doing that
This works as well
if object_id('tempdb..#test') is not null drop table #test;
declare @database_name varchaR(100) set @database_name = 'master'
declare @test table (owner sysname, object sysname, grantee sysname, grantor sysname, protecttype sysname, action sysname, [column] varchar(1000))
create table #test (owner sysname, object sysname, grantee sysname, grantor sysname, protecttype sysname, action sysname, [column] varchar(1000))
declare @sql varchar(1000)
insert #test
EXEC ('EXEC ' + @database_name + '.dbo.sp_helprotect')
--set @sql = 'insert #test EXEC [' + @database_name +'].dbo.sp_helprotect'
--exec(@sql)
insert @test select * from #test
select * from @test

Open in new window

0
 
LVL 60

Assisted Solution

by:chapmandew
chapmandew earned 120 total points
ID: 34148076
You can nest execs easily enough:  exec('exec(''exec sp_who2'')')

the problem was the table var in 2000
0
 
LVL 6

Author Comment

by:anushahanna
ID: 34148492
y'all excellent!
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Introduction SQL Server Integration Services can read XML files, that’s known by every BI developer.  (If you didn’t, don’t worry, I’m aiming this article at newcomers as well.) But how far can you go?  When does the XML Source component become …
Everyone has problem when going to load data into Data warehouse (EDW). They all need to confirm that data quality is good but they don't no how to proceed. Microsoft has provided new task within SSIS 2008 called "Data Profiler Task". It solve th…
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question