Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.
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
Asked:
-
2
- +2
1 Solution
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.
You can usually get around reserved words be enclosing them in square brackets like so: [function]
Not sure if that will work inside openquery though.
Not sure if that will work inside openquery though.
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?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
That is probably the best way to think of this.
HTH,
Kent