Can someone help in answering my queries.
1. Will I be able to run 2000 DTS in SSIS.
2. Which one is easier DTS or SSIS. I have come to know that SSIS is like informatica and no need to right big big stored procedure as we do in DTS for ETL.
3.If I make a part of Datawarehouse in DTS and the other in SSIS, will everything work.
4.If suppose i have shared dimension "X".in the first phase it is populated by DTS and in the 2nd phase can i also polulate by SSIS simultaneously.
1 Yes, but it is really a backward compatibility thing. SQL 2005 includes the ability to run DTS packages, but there is no effective upgrade path for DTS packages to SSIS packages. I generally advocate re-writing DTS as SSIS to get the benefit.
2 SSIS, unless you have a big DTS mindset to overcome. A little effort up front to get your eyes open to the tools available, and it should be easy going forwards
3 Yes probably, but just sounds wrong as the two are so different. Ongoing maintenance for a start would be horrible because it means support staff always need to know two technologies.
4 Yes, if we are talking about the tables, perfectly possible, it is after all just a table, so you can do what you want.
|||I generally agree with Darren on the answers to your questions.
I would like to add a little comment though. Do you have any idea when you will be able to start working with SSIS? If you plan to move to SQL 2005 anywhere soon, I would strongly advise _not_ to start in DTS. As Darren states, if you have a DTS mindset, SSIS probably gets more difficult te learn. Besides, you will end up using two ETL tools. So you need to maintain your ETL using two tools, need the knowlegde of both...
Besides, you can use SSIS and still have a SQL 2000 datawarehouse. Just run SSIS on a separate server, and leave your source and DWH databases running on SQL 2000.
Regards,
Pipo1
|||2. DTS is "easier" - but scripting sucks (activeX only without any good designer). On the other hand i still write Stored Procs in SSIS - nothing compares to good ol' SQLGo with SSIS if possible - it can populate SQL 2000 database. If mandated by management to use DTS - theres not really an easy upgrade path for the packages - IMHO - all Dts packages need to be rewritten (e.g. activeX scripts, Data sources in SSIS have datatypes etc.)
3. Mish & mash usually tends to be a headache|||
Kind of repeating what other people have said but nonetheless....
Ag_dwh wrote:
I worked mainly on informatica , butmy company want me develop a datwarehouse using SQL Server.Presently they have SQL Server 2000. They want the first phase to be on 2000 using DTS and then subsequent phases in 2005 SSIS. Can someone help in answering my queries.
1. Will I be able to run 2000 DTS in SSIS.
Yes.
2. Which one is easier DTS or SSIS. I have come to know that SSIS is like informatica and no need to right big big stored procedure as we do in DTS for ETL.
The answer is "it depends". if you have an Informatica background then SSIS will definately be easier. This may help:
Conchango Describes How SQL Server 2005 Integration Services Compares with Informatica
http://www.microsoft.com/sql/technologies/integration/conchango.mspx
3.If I make a part of Datawarehouse in DTS and the other in SSIS, will everything work.
You can have your data warehouse in SQL 2000 and your ETL done in SSIS. is that what you mean?
4.If suppose i have shared dimension "X".in the first phase it is populated by DTS and in the 2nd phase can i also polulate by SSIS simultaneously.
Yes.
-Jamie
|||
this from a (relative) newbie to SSIS...
i was hooked on DTS and intimidated at first by SSIS. The initial learning curve is a bit steep but it's not difficult -- and once you get the basic understanding of Connection Managers and the myriad NEW tools available, there's no turning back. And it's very easy to re-direct packages from one environment to another (dev to testing to production).
seth j hersh
No comments:
Post a Comment