[dba-SQLServer] SSIS, SQL Server Integration Services, DTS

Gustav Brock Gustav at cactus.dk
Fri Jan 18 12:14:10 CST 2008


Hi Arthur and Robert

Just realised what the SQL Server Configuration Manager is for ...
It showed that I have two SQL 2005 Servers installed locally, SQLEXPRESS and MSSQLSERVER. Of these, the first is the Express edition I guess (from a previous install of Visual Studio 2005 Express) and the second must be the developer version installed with VS2005 Standard.

The second wasn't running. I started it and somewhere I noticed a tip to create a DTS package: Run DTSWizard from Start Menu, Run.
That wizard connected happily to a server and offered to save and run the created SSIS package ... OK, and yes it did. Success!

Now I need to find out how to get to that saved package ...

/gustav

>>> fuller.artful at gmail.com 18-01-2008 17:40:08 >>>
Gustav,

Packages are YOUR creation not MS's. You can deploy your own creations as
far and wide as you please. Just don't fill my kitchen with them! LOL.

On 1/18/08, Gustav Brock <Gustav at cactus.dk> wrote:
>
> Hi Arthur
>
> Well, we don't have a SQL Server 2000 here except for the MSDE engine
> which I believe came with poor management, if any.
>
> On the other hand, we do have the 2005 Standard from the Action Pack -
> just never installed it as we haven't had anything to use it for.
> I could do so, of course, including the SSIS, and - as I understand - then
> create a package. But could I move that package to the client's SQL Server
> 2005 Express installation without licensing issues? It should be added, that
> the cost of even a basic Standard license with 5 CALs is prohibitive and
> that the database will be some hundred MB only, thus the Express version
> fits well.
> Finally, the client doesn't have any SQL Server installed, so there is
> nothing to migrate. That said, the client would probably not have any use
> for the new fancy features of 2005, and the user count will be of less than
> five, thus the MSDE could be used if just looking at the database need only.
> But I've heard nothing bad of 2005 so that would be my first choice. The
> client doesn't care - wouldn't even know what I was talking about.
>
> /gustav
>
> >>> fuller.artful at gmail.com 18-01-2008 16:51:06 >>>
> I could be wrong and this is "off the top of my forehead", as it were, but
> I
> think that to go where you wish to go, you need a box with SQL 2000 and
> SQL
> 2005 installed. Then you can create the DTS pkgs in 2000 and run them in
> 2005 should you wish to do so.
>
> Another alternative, which I'm sure applies to Europe as well as North
> America, is to attend the roll-out for SQL 2008, VS 2008 and SharePoint
> 2008. Here in Toronto they are giving away copies of these three to all
> attendees. Mind you, these are developer copies, not production copies, so
> maybe that doesn't help your client.
>
> A larger question emerges, in this context. Why is your client moving to
> SQL
> 2005 (or 2008 for that matter)? If SQL 2000 does everything required, why
> move? I am a huge fan of the improvements in 2005, but if you don't need
> them, why migrate? SQL 2000 is perhaps the most rock-solid product
> Microsoft
> ever delivered, and if you cannot point to a concrete reason to move past
> it, stay where you are, in the comfort zone.
>
> hth,
> A.
>
> On 1/18/08, Gustav Brock <Gustav at cactus.dk> wrote:
> >
> > Hi Arthur
> >
> > Thanks. I think I can stick with DTS as the tasks will be quite simple.
> > But where do I go? I located this:
> >
> > Microsoft SQL Server 2000 DTS Designer Components
> >
> > The Microsoft SQL Server 2000 Data Transformation Services (DTS) package
> > designer is a design tool used by developers and administrators of SQL
> > Server 2005 servers to edit and maintain existing DTS packages until they
> > can be upgraded or recreated in the SQL Server 2005 Integration Services
> > package format. After installing this download, SQL Server 2005 users can
> > continue to edit and maintain existing DTS packages from the Object Explorer
> > in SQL Server 2005 Management Studio and from the Execute DTS 2000 Package
> > Task Editor in Business Intelligence Development Studio, without needing to
> > reinstall the SQL Server 2000 tools. The DTS package designer in this
> > download was formerly accessed from the Data Transformation Services node in
> > SQL Server 2000 Enterprise Manager.
> >
> > and downloaded and installed the file "SQLServer2005_DTS.msi".
> >
> > But now what? Close reading reveils "existing", so can't a new DTS package
> > be created?
> > I relaunched my "Microsoft SQL Server Management Studio Express" but the
> > only item regarding DTS was found under Providers: DTSPackageDSO ...
> >
> > /gustav




More information about the dba-SQLServer mailing list