Options
Temp tables from Oracle linked server
MikeyC
Posts: 249 Bronze 3
I know linked Oracle servers aren't supported, but given the sample code below, would it be possible to at least support the temp table object itself, and maybe the field names that are selected?
SELECT Distinct t.tx_id,
t.match_trx_id,
t.detail_type,
t.proc_id,
e.proc_code,
e.proc_name,
e.proc_cat,
e.proc_group_id
INTO #Adj
FROM edic..Fuzz.Fuzz_TLD t
INNER REMOTE JOIN edic..Fuzz.Fuzz_EAP e
ON t.proc_id = e.proc_id
WHERE t.detail_type = 30
ORDER BY t.tx_id;
SELECT * FROM <cursor>
#Adj isn't a suggestion at this point, and it doesn't know any fields that are in #adj.
I fully understand if it won't be supported because of the remote link to Oracle, it would just be nice.
SELECT Distinct t.tx_id,
t.match_trx_id,
t.detail_type,
t.proc_id,
e.proc_code,
e.proc_name,
e.proc_cat,
e.proc_group_id
INTO #Adj
FROM edic..Fuzz.Fuzz_TLD t
INNER REMOTE JOIN edic..Fuzz.Fuzz_EAP e
ON t.proc_id = e.proc_id
WHERE t.detail_type = 30
ORDER BY t.tx_id;
SELECT * FROM <cursor>
#Adj isn't a suggestion at this point, and it doesn't know any fields that are in #adj.
I fully understand if it won't be supported because of the remote link to Oracle, it would just be nice.
Comments
Actually in all seriousness we do pick up "unresolved" table names in the FROM clause in many cases so it wouldn't be easy to add such unresolved columns listed in the SELECT column list. It's something we'll definitely consider for the future.
Cheers,
Bart
Principal Consultant
bartread.com Ltd