Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
p2bl
Yak Posting Veteran
54 Posts |
 Posted - 2002-06-30 : 05:06:12
|
| When I use DTS to import/export a whole database,I find some nested views cause errors.For example,there is a view called vu_a,and another view called vu_b,"vu_b"'s DDL may look like this:<i>select column_a from vu_a</i>and the DTS error is:Invalid object name "vu_a",things like that befor transferring vu_b,vu_a is not transfered.Please help me!thnks a lot!========================look! |
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-07-01 : 09:59:04
|
| This problem with the 'Transfer database objects' task has infuriated developers for years ...The issue isn't nested views per se but rather an inability for the DTS engine to script out the objects in the proper order. If object A references object B, for example, you can't create object A first - it won't compile as it refers to a not-yet-in-existence B.If your objective is to 'copy' or 'update' a database from a source database in its entirety, use a backup/restore mechanism. If you are unfortunately moving only a subset, you'll need to build a DTS package that has several steps, one for each dependency layer.Jonathan Boott, MCDBA |
 |
|
|
p2bl
Yak Posting Veteran
54 Posts |
Posted - 2002-07-02 : 06:29:53
|
| OH My God!!There's at least 100 views in this database!========================look! |
|
|
|
|
|
|
DTS fail with nested views