Is there a reason to store the data twice? That's what you're doing since you have a clustered index on the ID column, and a non-clustered index on every...

Couple of options.

You could do a second command that would select the characteristic desired for the stated database and find out if it's changed or not.

You could switch to sp_exececutesql...

Can you post the table definitions and the execution plan for the update?

I'd have to know your actual table structure or use of this to do more, but see if this gets you going in the right direction:

declare @IPRange varchar(100);

select @IPRange =...

Yep. 🙂

lexicographicolatry

Try this:

select *

from sys.dm_db_index_physical_stats(db_id(), null, null, null, 'detailed');

That'll get you all the indexes in the database you are connected to in Management Studio.

If you want only one table, put the...

Right-click on the index in Management Studio and go to Properties. It'll have the size in there.

Or, you can select from sys.dm_db_index_physical_stats and get the depth, fragmentation, pages, space...

You can add conditional handlings to the flow-control objects in DTS. Right-click the green arrow (the flow-control object), and I think you then go to Properties and walk through...

There are probably thousands of different things that could cause this, ranging from file corruption to lack of a primary key on the target table.

We would need significantly more information...

Take a look at sys.dm_db_index_physical_stats and sys.dm_db_index_usae_stats in Books Online. Those should have what you need.

You're welcome. Took me two weeks to figure it out the first time I ran into that. I take every chance I get to spare the pain for...

I generally use a staging table for that kind of thing. Import the whole thing into one table, then split it up in there with appropriate queries, in order...

You need to set IMEX=1 in the connection properties. Google/Bing/whatever "IMEX" and you'll find the syntax for that, and some notes about what you may need to do in...

Seems kind of odd having a table with just an ID column in it, but it looks correct in this case.

That looks like the right design for what you've described.