Not only is it a bad idea to create a trigger on a system table, but the good engineers at Microsoft have prevented it.

You probably want to create a DDL...

The simple version of the rule is the more read and write heads you have accessable for operations, the better performance you will get. So, if you can have...

You should post SQL 2000 questions in a SQL 2000 forum.

The relationship table - I thought it was all in the one table from your previous email.

You can create a many-to-many relationship in a cube, but it is not really a hierarchy.

In your case, "Countries" will contain the relationship between your facts and your "Country Groups".

So,...

The system table structure changed significantly in SQL 2005.

The sysdatabases table is no more.

Search this site a little. There are lots of postings for how to search procedure text. It is not hard to search the syscomments view, but there are...

I am not sure if you are aware, but by default replication replicates one row at a time.

So, since you deleted 13 million rows, the distribution agent needs to run...

While it is running, run the procedure sp_who2 and make sure no processes are blocking it.

DDL changes can get blocked by other processes pretty easily.

The DCOM settings are what you need to fix. You have either found bad instructions, or you missed something.

When you install SQL, you get a SQLServer2005DTSUser.

Adding your developers to...

Also make sure you don't have the file open from your workstation.

Ok, I am going to make some assumptions.

1) You have a data flow task that is writing your data to two text files (X and Y records)

2) You want to...

You can do what you are indicating. Search around for dynamically setting connection properties and you should find an article or two. I'll search google a bit for...

You could use a script task to read in the ini file, parse it, and set variables and properties with it.

However, using package configurations would be much easier.

Trouble with your homework?