Ignore Richard and the bastard, this is an appropriate question in the correct forum. Unfortunately your question is a little too broad to elicit a reasonable response. SSIS is such a wide subject. I do know that we moved from ETL to ELT where the transforms are done via stored procedure. It is faster and I find it easier to debug and test. So SSIS just moves the data from the source into staging tables and launches the transform stored proc.
Never underestimate the power of human stupidity RAH
According to this KB article[^], SQL 2012 should be able to rebuild the index online. Try installing SP3[^], possibly followed by the latest cumulative update[^]. Or, if you've got SP2, install CU4[^] or one of the later cumulative updates[^].
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Right. It can be a bit tedious. I've been working on a project for a few months, an existing application. The new enhancements/features required that we split some existing tables out (moving a field from one table to a new table). When setting up the deployment, I had to alter the generated diff scripts quite a bit.
djj55: Nice but may have a permission problem Pete O'Hanlon: He has my permission to run it.
There is a right tool for this job. DBConvert. Convert / Sync from Microsoft Access to Microsoft SQL Server[^] DBConvert/ DBSync for Access and Microsoft SQL Server are powerful cross database migration tools for upsizing and synchronization of Access x86/x64 data to MS SQL Server. Good: - This does almost everything related to cross dbs. Database migration, conversion, export.. etc. - Daily scheduler is quick Bad: - May be expensive for personal use - Need to spend some time when you are implementing/configuring
I needed to have SSIS run time on my machine where I am executing the Console app, or reinstall SQL Server along with Integration Services.
Thanks, Abdul Aleem "There is already enough hatred in the world lets spread love, compassion and affection."
Thank you for your reply. All of our shared datasets point to stored procedures. I think I just figured out a solution. I have done this before. I don't know why I didn't think of it before. I am going to have my program download the shared dataset as an .rds file and then look at the xml tag CommandText in the rds file.
I got it resolved my friends, no worries right now :)
Thanks, Abdul Aleem "There is already enough hatred in the world lets spread love, compassion and affection."
It's been 15 years since I touched Access, does that represent short memory loss I wonder. While I think Access has it's place, the moment it moves to a server or shared drive it becomes the wrong tool for the job.
Never underestimate the power of human stupidity RAH
