That's true, I assumed the database server is under the control of the DBA and any change is subject to a proper change control process.

But I sure agree with...

Nice input Lempster, storing configuration settings in a table makes it possible to set very granular permissions. But configuration files in XML format can also be secured using Access Control...

David, if you create a new system environment variable, you may have to restart the system, but for a user environment variable, you may have to log off and log...

You can place the package configuration file in any location. What is important is for you to select the appropriate configuration file during deployment and to ensure the file can...

Storing your configuration file as XML is only one of the options available. Your choice will depend on your work environment and what fits into it.

Using XML is just...

To resolve this issue , I'll suggest the following:

Create a destination variable e.g Dest_Var

Set its EvaluateAsExpression to "True", and copy and paste the expression you created above into the variable's...

Absolutely, you can use variables to supply values at runtime to your SSIS task. You just have to create the control flow using a combination of control flow tasks and...

To fix the error, set the ReadOnlyVariables property of the Script Task editor to "Path" and not

"User::Path". You don't need to qualify it with the namespace.

Also, you don't need...

You can use Execute SQL Task to achieve this. Set the Resultset to "Single row", SQLSourceType to "Direct input" if you'll be typing in the sql statement instead of using...

Yes, SQL server 2005 has predictive analysis tools. You use SQL Server Analysis Services (SSAS) to perform data mining tasks like creating predictive models using decision tree, naive bayes etc.

Set the "Bypass Prepare" property to "True" .

Cheers!

Yes you are right, db_ssisadmin is in 2008. if you don't mind, i'll suggest you do a clean deployment of your package and test it before scheduling.

If this works fine,...

Did you set Bypass Prepare to "True"?

When configuring the Execute SQL Task, set the resultSet to "None" and Bypass Prepare to "True"

and you should be fine. 🙂

Try this with your initial code.

Cheers!

Nothing else to do and you don't need to click on the build query button.

Just click on the Ok button, and to test if it works fine, right-click on the...