November 5, 2009 at 2:47 am
I AM NEW TO SQL DBA. I AM LEARING THE NEW THINGS IN SQL SERVER WHAT IS SSIS IN SQL SERVER AND ITS FUNCTIONS .
WHAT IS DTS IN SQL SERVER AND ITS FUNCTIONS .
November 5, 2009 at 5:48 pm
These technologies are for different platforms. DTS is a SQL 2000 technology standing for Data Transformation Services. It provides COM+-based tools to build packages to perform ETL operations on data.
SSIS (SQL Server Integration Services) is basically what DTS evolved into for SQL Server 2005 and beyond. It takes more advantage of the .Net framework and is different in how a package is designed. More complicated, but supposed to be more powerful too.
You can get really deep into both of these technologies. If that is what you are looking for, I would suggest to pick one (probably SSIS if your environment has more SQL 2005/2008 usage) and come up with some projects that you can use to learn about one of these.
Joie Andrew
"Since 1982"
November 5, 2009 at 9:09 pm
Although you can run DTS packages on SQL 2005/2008 you cannot create new ones. SSIS is a quantum leap over DTS in what it can do. Basically everything DTS can do SSIS can do better.
I think the learning curve is a little steeper on SSIS but once you got it down it works great.
To be honest with you you should not be doing ANY new development on SQL 2000, it is effectively end-of-life with Microsoft, and while support continues for a while there have been 2 full version releases since it was released.. Upgrade..
CEWII
November 6, 2009 at 12:53 am
That may not be a choice though. I know I still support many applications that my organization either does not have the will to upgrade to yet, or there is no equivilent upgrade yet, so I am stuck supporting those SQL 2000 boxes for the time being. It is a business decision, and sometimes there is little that can be done to sway that.
However, I agree that if you can upgrade, do it.
Joie Andrew
"Since 1982"
November 6, 2009 at 7:44 am
I fully understand the need to support SQL 2000, but as SQL 2000 is nearly 10 years old, now would be a good time to let those holdouts know that it is end-of-life and that a date not too far in the future there won't be any vendor support for it. As it is right now you will pay for any incident you open with them even if its a bug in their code.. Everybody on 2000 should consider an upgrade, I know of a few instances that people are still on 6.5 and 7.0 and they had no choice because of the package they are running, but they are taking a risk, and they know it..
Bottom line, start the conversation with them on upgrading.
CEWII
November 6, 2009 at 8:48 am
It's a valid point that many businesses still have SQL 2000 servers, and will continue to have them for some time yet. Could be a niche market in the future.
But if you are new to SQL Server, I recommend focusing on SQL 2005/2008. That means SSIS in this case. You could focus on SQL 2000, but that'd be like taking the time to learn COBOL. Yes, there's a market for that, but it's pretty well filled by people who already know it, and it's getting smaller every year.
Learn what you need to for SQL 2000 in order to do your job, but spend more time on 2005/2008, since that's where the jobs are going to be in future years. Otherwise, you're competing against people with years of SQL 2000 experience for a dwindling number of jobs.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply