468,244 Members | 1,730 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,244 developers. It's quick & easy.

Select into / Linked Server / Missing IDENTITY attribute

Greetings,

If I use a "select into" to clone a table, all attributes are created
correctly, however, if I use the same statement across a linked server,
my identity column loses its IDENTITY specification.

Is this a known issue or basic functionality of using "select into"
with linked servers?

Kurt

Nov 28 '05 #1
2 6384
(kh******@qwest.net) writes:
If I use a "select into" to clone a table, all attributes are created
correctly, however, if I use the same statement across a linked server,
my identity column loses its IDENTITY specification.

Is this a known issue or basic functionality of using "select into"
with linked servers?


I don't know if it's documented, but it makes sense. With a linked table,
SQL Server has knowledge about metadata in a more generic format. That
linked server could be something radically different from SQL Server,
for instance Oracle.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Nov 28 '05 #2

"Erland Sommarskog" <es****@sommarskog.se> wrote in message
news:Xn**********************@127.0.0.1...
(kh******@qwest.net) writes:
If I use a "select into" to clone a table, all attributes are created
correctly, however, if I use the same statement across a linked server,
my identity column loses its IDENTITY specification.

Is this a known issue or basic functionality of using "select into"
with linked servers?
I don't know if it's documented, but it makes sense. With a linked table,
SQL Server has knowledge about metadata in a more generic format. That
linked server could be something radically different from SQL Server,
for instance Oracle.


And serves as a good example of why Celko is continually ranting (I want to
say warning but let's call a spade a spade) about the dangers of using an
IDENTITY column.


--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Nov 29 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Christopher Brandsdal | last post: by
5 posts views Thread by Daniel Wetzler | last post: by
reply views Thread by kermitthefrogpy | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.