Table Properties export

Question

Table Properties export

dmiller-745870

Mr or Mrs. 500

Points: 550
More actions
February 4, 2010 at 4:55 pm

#216339

When I export tables to a different DB the properties (Index/Key, etc.) don't follow. Is there a workaround for this? And can I overwrite the table in the target DB, instead of deleting the tables before performing the export process? Thx in advance ...

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Bru Medishetty SSC-Insane Points: 23606 More actions · Answer 1

How are you performing this? Are you using just the Import/ Export Wizard or using script table and move it manually?

You would be better if you are using the generate scripts task (Rt click the database and in tasks, you find it and there you can select your table(s) and when generating scripts, you can additionally choose to generate Drop if existing, generate Index(es), other constraints etc...

Actually if you have SQL Server 2008 SSMS (not the Server, only your SSMS as 2008), you can even script the table, its properties, indexes etc along with that, the data also, so what happens is that you have a insert into table statement also scripted, which can be used.

Bru Medishetty

Blog -- LearnSQLWithBru

Join on Facebook Page Facebook.comLearnSQLWithBru

Twitter -- BruMedishetty

SQLRNNR SSC Guru Points: 281334 More actions · Answer 2

If you want the indexes and such to follow, you should script it out and execute that script on the destination. Another option is to use a tool Such as RedGate SQL Compare.

Otherwise, an import/export operation is typically the data.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Jeff Moden SSC Guru Points: 1004361 More actions · Answer 3

Sorry... posted to the wrong thread...

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)