I usually try to make the name of the constraint really descriptive. The default raised error from SQL contains the constraint name.

Yes, the Slowly Changing Dimension Transformation component.

Although designed for dimensions, it will work for any "insert or update" situation.

It is really a wizard and a component that compares a data...

Honestly, you covered the hard part - getting an OLEDB driver to work with your AS400 can be a pain.

As far as copying the data, it will depend on the...

Ok - I'll bite. If you put the two indexes on different file groups, and then put the different file groups on different physical drives, and then ran queries...

You have everything right - add the constraint and the NOT NULL and you are in good shape.

The errors are simply that you have some index on the table that...

I have never tried to do that either, but it makes sense. If the installer detects any instance of SQL, it may not want to allow anything but a...

NOLOCK reads dirty pages, so by inconsistent data I mean your application may present data not only uncommitted data that could be rolled back, but you cound, in fact, read...

NOLOCK would just give you a bunch of inconsistent data anyway, so using it here is probably a really bad idea (it is usually a bad idea to use that...

Your trigger will also not work correctly if more than one record is inserted at the same time - triggers in MS SQL are set based, the INSERTED table can...

You want to change the INNER join to a FULL OUTER join and then use the WHERE to give you records that do not have a match.

[font="Courier New"]SELECT

*

FROM

Information_Schema.Columns A

FULL OUTER...

It seems to me like you are trying to solve a problem that does not really exist.

Let me recap - you have a logging scheme that needs to track some...

MS SQL 2005 will use multiple threads even with a single filegroup. You can increase performance in some instances by spreading your queries over several filegroups because you can...

Assuming you have both databases test and test2 running on the same server:

[font="Courier New"]use test

select testTable1.*

into test2.dbo.testTable1

from testTable1

go[/font]

I had the same result as Tim, I re-created this and the original logic worked fine.

Check your data types on your source data in the Advanced Editor to make sure...

To follow MS guidelines, use the Information_Schema views:

SELECT * FROM Information_Schema.Columns WHERE Column_Name = ''