I never understand why people want to buy these expensive products when they already have SQL Server, SSIS, SSAS and SSRS running which can do the job.

Maybe they think...

VB should be the start as SSIS uses it and particularly VB.NET. I'd recommend a course first but my favourite website for getting to grips with vb.net web apps was...

Parent package variables work well for me with a config file driving the parent package and that setting and passing variables to its children - the config file holds the...

We went through this process, gradually migrating three thousand users. It was a pain but life is a lot simpler if you use only groups for access to sql servers...

Flat file logging can be easier to follow when starting logging.

Right click the connection manager and select Edit and play with the settings. You can add more columns using the Advanced tab.

Tip: you don't have to stick to the delimiters...

I backup loads of servers using sql agent jobs and step1 does the backup using the TSQL backup command and step 2 is an operating system (CmdExec) copy command to...

I'd get the separate dev and test app and database environments set up and working and run the everyday, period end, month end, year end and any other time procedures...

My son is an unpaid intern in Sweden as his sandwich year of university (BSc multimedia and animation). Thank goodness for ERASMUS (European students abroad scheme) and UK student loans...

I think there's too many upgrades too soon, especially for both large companies and home users who can't afford to keep upgrading when the old one still works fine, especially...

The problem of possibly changing databases should be catered for in the actual application code by using a data access layer that can be changed according to the database used,...

Fire up the SQL2000 enterprise manager tool, connect to the server (like Management studio on 2008) and selct "data transformation services" to see the packages on that server. Right click...

How about setting it up as a SQL Agent job with no schedule that runs the package under a proxy account and giving them permission to execute the job with...

Why not take a step back and create your SSIS export by querying the tables used to create the cube?

It's just the same as the proliferation of Access databases and Excel spreadsheets out there and we have to control those somehow!