bulk insert with a primary key?

i'm using sql2k.
can i do a bulk isnert operation to a table with a primary key
(identity field) on it? i suspect the dts pacakge didn't utilize the
bulk insert because pk is automatically a non-clustering index, and
bulk insert can only work on table w/o any index. in this case, what
should i do to make sure the fastest load possible?
thank you.> bulk insert can only work on table w/o any index.
Since when? I have several applications where BULK INSERT affects a table
with a clustered index on a datetime column and a non-clustered index on a
foreign key column. The only way it differs from your scenario is that all
the data is in the file (there is no surrogate column generated by the
system).

> in this case, what
> should i do to make sure the fastest load possible?
As long as the generation of the IDENTITY values does not need to correspond
directly 1:1 with the physical order of the file, you may wish to bulk
insert into a heap, and then insert real_table(column_list) select * from
heap.
A|||It is not true that bulk insert will only work with non-indexed tables.
In fact, you can achieve better throughput, if you have a clustered index on
the table, and input file is also sorted in the same order as the clustered
index.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"=== Steve L ===" <steve.lin@.powells.com> wrote in message
news:1123518093.288607.254270@.g14g2000cwa.googlegroups.com...
> i'm using sql2k.
> can i do a bulk isnert operation to a table with a primary key
> (identity field) on it? i suspect the dts pacakge didn't utilize the
> bulk insert because pk is automatically a non-clustering index, and
> bulk insert can only work on table w/o any index. in this case, what
> should i do to make sure the fastest load possible?
> thank you.
>

Bulk copy out of table error

I had to restore my msdb and distribution databases at my DRP site because
they went SUSPECT on me. I had scripts to create and delete the subscriptions
to three of my database. I ran the scripts and all but one is working. The
snapshot error message I receive is "The process could not bulk copy out of
table '[dbo].[syscobj_0x3534373544363843]'. Of course I do not have a table
with that name. I am very new to SQL world and any help will be greatly
apprecitaed. I have tried reinitializing the subscription and also deleted
and recreated the subscription but nothing is working.
this is not a table but a view. It is a view of the underlying table. The
best way to try to resolve this problem is to try to query the view
directly, i.e.
select * from syscobj_0x3534373544363843
Also can you do this
sp_helptext syscobj_0x3534373544363843
and post what you see back here?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"golfnut" <golfnut@.discussions.microsoft.com> wrote in message
news:5B547AEB-0B57-4200-8814-DE8CA253A5F5@.microsoft.com...
> I had to restore my msdb and distribution databases at my DRP site because
> they went SUSPECT on me. I had scripts to create and delete the
subscriptions
> to three of my database. I ran the scripts and all but one is working. The
> snapshot error message I receive is "The process could not bulk copy out
of
> table '[dbo].[syscobj_0x3534373544363843]'. Of course I do not have a
table
> with that name. I am very new to SQL world and any help will be greatly
> apprecitaed. I have tried reinitializing the subscription and also deleted
> and recreated the subscription but nothing is working.
|||Hi Hilary,
When I ran select * from syscobj_0x3534373544363843 the error message was
Invaild object name.
When I ran sp_helptext the errror message was The object does not exist in
database
Also, I went to agent history of the snapshot and there is another error
message the says Another snap shot agent is running but there is not another
agent running that I can see.
"Hilary Cotter" wrote:

> this is not a table but a view. It is a view of the underlying table. The
> best way to try to resolve this problem is to try to query the view
> directly, i.e.
>
> select * from syscobj_0x3534373544363843
> Also can you do this
> sp_helptext syscobj_0x3534373544363843
> and post what you see back here?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "golfnut" <golfnut@.discussions.microsoft.com> wrote in message
> news:5B547AEB-0B57-4200-8814-DE8CA253A5F5@.microsoft.com...
> subscriptions
> of
> table
>
>
|||Thanks for letting me know that number is a view. I went into my production
database and saw that the view was created on 1/11/05. This database at my
DRP site was restored in December. If I restore the latest copy of the
database should make this replication work properly.
Thank you very much for your reply but now I have another problem on a
different server at my DRP site.
If I click on the publication and look at the subscriber column the
subscriber name has changed to REPL_DISTRIBUTOR.
"Hilary Cotter" wrote:

> this is not a table but a view. It is a view of the underlying table. The
> best way to try to resolve this problem is to try to query the view
> directly, i.e.
>
> select * from syscobj_0x3534373544363843
> Also can you do this
> sp_helptext syscobj_0x3534373544363843
> and post what you see back here?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "golfnut" <golfnut@.discussions.microsoft.com> wrote in message
> news:5B547AEB-0B57-4200-8814-DE8CA253A5F5@.microsoft.com...
> subscriptions
> of
> table
>
>