I received a file with extension dts. I'd like to open it and print the query it contains. Can someone give me instructions as to how I can move it to Data Transformation Services in a new database then open, print and edit the query it contains? Thanks for any help!

In article <317E6254-B91B-4776-9297-87130B5971AF (AT) microsoft (DOT) com>, Sdhi wrote:
Using SQL Server 2000

Right Click on the Data Transformation Services folder | Open Package

In SQL Server 7

Right Click on the Data Transformation Services folder | All Tasks | Open Package



--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
www.konesans.com - for all your consultancy needs

Thanks. I've now got the file in the DTS folder. I can open it, but i don't see how to print out the query. Just copy and paste into notepad? I' m responsible for creating .str files that can be transformed using this .dts file. I have to create the .str files from 21 different sources. There isn't a data dictionary so I'm trying to work backward from the .dts file to see field names that the .str file transforms to. Then figure out how get a txt file into an .str file that will work with the dts. file. If you haven't guessed, I've no experience with SQL 2000 (and person who did this left with no documentation!) . Any further help would be greatly appreciated!

"Allan Mitchell" wrote:

In article <B5821588-6B4C-4359-8587-51F06BC7A815 (AT) microsoft (DOT) com>, Sdhi wrote:
I am not wholly sure what you want but

Query? Yes you can copy paste into Notepad but this will be a pain if you have

1. Lots of these in 1 package AND/OR
2. Lots of packages.

You can use the object model to grab properties of the package(s) and then do with them as you please.

What do you mean by Query?
Are you wanting to substitute these with your own strings after reading from your .str file?




Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
www.konesans.com - for all your consultancy needs

I'll try and explain - I get 21 different files from various sources that contain more, or less, of the information we need to extract. The information is basically the same-but the layouts and source of each file is different. I'm to look at each file and turn it into an .str file that can be added to the same table through Data Transformation. I'm trying to figure out the layout of the .str file. I have the Data Transformation package and the source files. I don't have the layout of the .str file that must be transformed. So - trying to work backwards from the DTS package to determine the layout of the .str file. If the query in the DTS package creates a field name "State" from the .str file field named "Field182", then I know the .str file must contain the state in Field182.

I do have a couple of old .str files that have the converted data from two sources. When I open them, they are in an ascii format (I think) with just a very long string of information for each record. There is no definition anywhere for the significance of each character in a record. That's my ultimate goal. To move the source data into identical str files then send the str file on to the SQL2000 table. Since there's no documentation and all I have is the original data and the DTS, I'm trying to reproduce middle of the process - creating identical .str files from the source data.



"Allan Mitchell" wrote:

In article <5FC8FCD7-151C-4D84-B05B-C62598CA4ADF (AT) microsoft (DOT) com>, Sdhi wrote:

So you have n Source files of n formats.
These will all go into the same destination table?
The Source files may contain attributes previously unseen?
If this is true then you will need to create the attribute on the destination and add it?
You will then need to map the new attribute in the source to the destination attribute?


If the above is true then the only way I can see for you to do this is to be very dynamic.

You read the first row in the source to determine attribute name
You read the table to determine attribute names

You issue ALTER table statements for those that do not exist

You then need to redo your SourceColumn and DestinationColumn properties as some of the columns listed may now not exist in this particular file and it will error
You add Transformation objects for each Name:Name pairing.

Have I got the situation correct?





Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
www.konesans.com - for all your consultancy needs