Microsoft
Software
Hardware
Network
Question : SSIS/TSQL Three Part Naming for Temp Table
Hi guys -
I have a SSIS package that gathers data from 2 different servers.
In one of my sql tasks I create a temp table (data put together by both server a and server b). I select the connection to be [connection1] (i have 4 in this package). Then I go and drop a data flow task after the execute sql task. Connection is [connection1], sql command text is "SELECT * FROM ##TempTable"
Well I keep getting this error:
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E14 Description: "Invalid object name '##TempTable.".
I'm thinking that it's because it may be creating it on the wrong server - but I'm not entirely sure how to test it.
All connections are set to RetainSameConnection = True
Can I do 3 part naming for a temp table (global temp ##)? Would that fix it?
Thanks!
Answer : SSIS/TSQL Three Part Naming for Temp Table
There are a few different ways. I've always used ADO. See
http://www.codeproject.com
/KB/vbscri
pt/simple_
sp_vb6.asp
x
L
Random Solutions
How to use the processing core library to create a PIMAGE in Java Netbeans?
Importing Custom Exchange Public Folder Data into Access 2007 table
get wrong autodiscover server in warning message....
Screen Saver Group Policy make different for user groups
OCS 2007 R2
C# WMI query for getting current logged on user doesn't work on Windows 7
Open file Security Message
Date Formula deducting today's date from date field
'System.Xml.Linq' doesn't contain any public member
SSIS Case Statement not executing