Thanks Trent.



Have a good weekend!

You too,amigo

Greg,

Did you notice that the SFSAuditDataActions and SFSAutodDataFields are in your package twice?  Just smoke one of them and see if the issue persists.  I will check to see if I need to make an import change to prevent this from happening again in the future, but this is probably the crux of your issue.

That helped, but still issues. It is barfing on the a couple of the SF security views, with this error:





I'm attaching the package and the log file.

Also, I'm also having problems managing my filegroups. I just have one (PRIMARY), but in some cases, the file was not originally placed in the standard SQL server data folder, but in another folder. I just noticed that I now have two data files (plus a log file): my original and an updated one added by the DDT. So, two questions:



1. Is there any way to set a folder for the file(s)?

2. How do I get rid of the extra data (.mdf) file?



I sometimes wish learning all this stuff wasn't so painful



Thanks!

Ahhh...priorities.  You need to set the view priorities since one relies on the other.  This is a relatively new feature of the DDT.  It will need to look like this:

I went ahead and made your profile work, so if you do this you should be in good shape.

We are adding a new feature...literally as we speak here, that allows you to have pre and post scripts that execute.  You would have to write a pre-script that sets the folder for you...which honestly I recommend against.  This is a setting on the SQL Server side of things and when you start moving the MDF file locations...well...it becomes a full time job and your responsibility instead of SQL Servers.  But if you have this need you will be able to set the folder location via a pre-execution script in the next update.

If it is not in use, then just "smoke it"  but if it IS in use, then you may have to detach it first.  Again, this would need to be done via a script...or manually through the Management Studio.