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
Solved

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

Posted on 2010-11-16
11
534 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
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
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

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

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

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…
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.

791 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