There has to be some outstanding variables here. Compare the problematic column datatypes to working datatypes. You can also see if using substring returns the same results.

SELECT SUBSTRING...

You can do something like this. Note you can change the update to a select statement to confirm that the data you are updating is correct. I have...

I dont think you can use try catch. You will have to take the tedious road for udfs.

This link may help you.

http://www.sommarskog.se/error-handling-I.html

What do you mean by structual changes to the database? Mirroring provides a redundant copy of the data. What exactly are you trying to accomplish?

just another thought... You can use union all also.

select * from table1 union all

select * from table2 union all

select * from table3 union all

....

select * from table 7

The full outer join will work.

If you are simpling comparing tables then making updates/inserts/deleting, I really do not forsee a problem.

Some things to note are:

- certain features are available for 2005, that are...

The question I am asking myself is why are you joining the table for the insert. Why didn't you just insert from each table, like:

insert into Customer_test

select * from...

When you use joins, you are telling SQL to give you all the customers that have matches in each of the joined tables. Right now, the only way a...

You can save your error log data in a table variable. Table variables are nonpersistent and therefore not rolled back. You can insert the table variable data into...

Thanks Matt sys.trace_events is much easier 🙂

You will notice the table is name sp. The online poster had a requirement where he wanted the table in the master database, thus the sp prefix.

I was thinking about this myself. I then found this online.

-- DEMO: Create an EventId table and populate it with definitions of each ID number

CREATE TABLE sp_EventID_Table (ID...

This may help you. This is a walk through of how to setup an instance in a clustered environment.

http://www.sql-server-performance.com/articles/clustering/cluster_sql_server_2005_p1.aspx

The default out-of-box for SQL 2005 is to have a default trace running. Not to be confused with the black-box trace which has a rollover at 5 or 10MB...