For Procs you will have to generate script in old DB and then execute it in new db after imporying tables and views. By the way whats exact nature of requirement that is forcing you to import DB?

Razov If you think this answer helps you please rate it, it helps me. :)

Try Save As option for solution there you can check for Encoding option.

Razov

Click Advanced Save Options Encoding should be Unicode (UTF-8).

Razov

Is your VB.NET project Unicode enabled?

Razov

I think using nvarchar should be sufficient. Although you'll not be able to see these characters in 'Query Analyzer' or 'Enterprise Manager' (you will see boxes instead) but when this data is called by client application e.g. C# you can see correct depiction of the character.

Razov

You are welcome.

Razov

For foreign key dependencies either you can look in th DB documentation(if any) or create a DB Diagram. Here is one query using the INFORMATION_SCHEMA views that returns both sides of all FOREIGN KEY relationships, as well as the name of the foreign key constraint.

SELECT
FK_Table = FK.TABLE_NAME,
FK_Column = CU.COLUMN_NAME,
PK_Table = PK.TABLE_NAME,
PK_Column = PT.COLUMN_NAME,
Constraint_Name = C.CONSTRAINT_NAME
FROM
INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS C
INNER JOIN
INFORMATION_SCHEMA.TABLE_CONSTRAINTS FK
ON C.CONSTRAINT_NAME = FK.CONSTRAINT_NAME
INNER JOIN
INFORMATION_SCHEMA.TABLE_CONSTRAINTS PK
ON C.UNIQUE_CONSTRAINT_NAME = PK.CONSTRAINT_NAME
INNER JOIN
INFORMATION_SCHEMA.KEY_COLUMN_USAGE CU
ON C.CONSTRAINT_NAME = CU.CONSTRAINT_NAME
INNER JOIN
(
SELECT
i1.TABLE_NAME, i2.COLUMN_NAME
FROM
INFORMATION_SCHEMA.TABLE_CONSTRAINTS i1
INNER JOIN
INFORMATION_SCHEMA.KEY_COLUMN_USAGE i2
ON i1.CONSTRAINT_NAME = i2.CONSTRAINT_NAME
WHERE i1.CONSTRAINT_TYPE = 'PRIMARY KEY'
) PT
ON PT.TABLE_NAME = PK.TABLE_NAME
-- optional:
ORDER BY
1,2,3,4

If you want to limit it to specific tables, you can add any of the following immediately prior to the optional ORDER BY clause:

WHERE PK.TABLE\_NAME='something' 

WHERE FK.TABLE\_NAME='something' 

WHERE PK.TABLE\_NAME IN ('one\_thing', 'another') 

WHERE FK.TABLE\_NAME IN ('one\_thing', 'another') 

Hope this solves your problem.

Hi, If you are deleting row from a table which has primary key referenced to other table as foreign key, Solution 1 - you will have to delete foreign key occurence of the data first and then delete primary key occurence or you'll get reference error which I think you are facing currently, Solution 2 - uou can force referential integrity between relations this will delete all forieign occurences on deletion of primary key but this solution is not recommended. Note: Truncate will delete all the record of your table and I'm not sure this will solve your problem anyways becuse truncate operation also will give referential error. hope this solves your problem Bi

Hi, for each tuple in source table you have to create 3 instances in destination table, you can do this via stored procedure, by help of various methods of choice. take temp table with columns [SrNo numeric identity(1,1)] and four column of source table. transfer source table into temp table take max SrNo in a variable say count for each row of temp table from 0 to count BEGIN insert destination table([source col1],[source col2],F1,[source col3] insert destination table([source col1],[source col2],F2,[source col4] insert destination table([source col1],[source col2],F3,[source col5] END I think this way will transfer all your record from source table to destination table in desired manner. Bi

can you give structure of tables you are talking about and structure of output you need?