SQL syntax with a restricted word
I needto execute a query to copy a complete table from one database (not on this SQL server) into a new database using a linked server. The complication seems to be that the table is named "FUNCTION"
--Select * into "FUNCTION from openquery(NEW,' select * from FUNCTION') this statement fails
I cannot rename the source table
--Select * into "FUNCTION from openquery(NEW,' select * from FUNCTION') this statement fails
I cannot rename the source table
SELECT INTO is reserved as you are trying to SELECT * INTO NEW_TABLE FROM OLD_TABLE
That is probably the best way to think of this.
HTH,
Kent
That is probably the best way to think of this.
HTH,
Kent
Kent
thats not going to be it as I have MANY other queries that seem to be working with this syntax.... It seems tio be related to the FUNCTION as the table name.
thats not going to be it as I have MANY other queries that seem to be working with this syntax.... It seems tio be related to the FUNCTION as the table name.
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Guessing the above square bracket solution would work.
I understand you can't rename the source table, but a possible workaround if the above doesn't work would be to create a view that does a SELECT * FROM FUNCTION, and save it as a name that isn't a reserved word.
>I have MANY other queries that seem to be working with this syntax
Hmm... if this is correct, and square brackets don't work, you might be somewhat hosed..
I understand you can't rename the source table, but a possible workaround if the above doesn't work would be to create a view that does a SELECT * FROM FUNCTION, and save it as a name that isn't a reserved word.
>I have MANY other queries that seem to be working with this syntax
Hmm... if this is correct, and square brackets don't work, you might be somewhat hosed..
So... I'm curious why you wouldn't fully qualify the table names since you're working with two tables in the same query with the same name, let alone the fact that it is a reserved word... brackets will fix SQL thinking your table name is an actual reserved command word...
I know you have a linked server connection in place but I'd definitely write it out as
[SERVER].[DATABASE].DBO.[F
What's the actual error that SQL throws at you on this?
I know you have a linked server connection in place but I'd definitely write it out as
[SERVER].[DATABASE].DBO.[F
What's the actual error that SQL throws at you on this?
Join our community and discover your potential
Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.
*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.