Showing posts with label import. Show all posts
Showing posts with label import. Show all posts

Wednesday, March 21, 2012

Installing Sql Server 2005 Side By Side with 7.0

I'm rather new at working with SQL Server. I've installed 2005 onto my PC and I have 7.0 already. What I want to know is how do I import my packages from 7.0 into 2005?

Any help would be appreciated.

Thanks

What packages are you referring to? Are you trying to move your databases? Did you upgrade to SQL 2005 or install a new instance?

Thanks,
Sam Lester (MSFT)

|||

The packages are DTS Packages that we have created. I installed another instance of SQL Server. So right now 7.0 and 2005 are running on the same machine at the same time.

Another question. When I installed SQL Server 2005 everything came up but I couldn't find a server name. My 7.0 has a server that I can browse and even had that before I did anything. So did I do anything wrong? Or are there additional steps that I failed to take?

Friday, March 9, 2012

Integer identity value handling in export / import

Hi,

I have a question regarding export / import when you have tables with autonumber (identity) columns as primary surrogate keys. Does export / import retiain the values of these columns so that referential integriy is not broken?

CharlesYes!
Depending on how you import the data, make sure you choose the correct option that you wish to explicitely insert your "own values" into an IDENTITY column.
You might want to check BOL for SET IDENTITY_INSERT or BULK INSERT...KEEPIDENTITY or BCP -E. There is also some equivalent when you use DTS, but since I don't use DTS, I don't know what option to check there.
--
Frank Kalis
Microsoft SQL Server MVP
http://www.insidesql.de
Ich unterstütze PASS Deutschland e.V. (http://www.sqlpass.de)|||

I am Hitesh.

I have the same issue. While exporting/importing data (from SQL 2005 to SQL 2005) IDENTITY column values get altered..this way my referencial integrity gets broken that is not good at all....I am familier that using COPY WIZARD & Backup/Restore this can be avoided but I want to know ONLY for DTS import/export wizard....Will you please help me....it's very very very urgent to me.

Thanks.

Integer identity value handling in export / import

Hi,

I have a question regarding export / import when you have tables with autonumber (identity) columns as primary surrogate keys. Does export / import retiain the values of these columns so that referential integriy is not broken?

CharlesYes!
Depending on how you import the data, make sure you choose the correct option that you wish to explicitely insert your "own values" into an IDENTITY column.
You might want to check BOL for SET IDENTITY_INSERT or BULK INSERT...KEEPIDENTITY or BCP -E. There is also some equivalent when you use DTS, but since I don't use DTS, I don't know what option to check there.
--
Frank Kalis
Microsoft SQL Server MVP
http://www.insidesql.de
Ich unterstütze PASS Deutschland e.V. (http://www.sqlpass.de)
|||

I am Hitesh.

I have the same issue. While exporting/importing data (from SQL 2005 to SQL 2005) IDENTITY column values get altered..this way my referencial integrity gets broken that is not good at all....I am familier that using COPY WIZARD & Backup/Restore this can be avoided but I want to know ONLY for DTS import/export wizard....Will you please help me....it's very very very urgent to me.

Thanks.