Microsoft SQL Server 2005 DTS Designer Components

Hi,

I learned this from one of SSIS book-Migrating from Data Transformation Services to Integration Services in SQL.

For the design time components, Microsoft has created a special distribution called the Microsoft SQL Server 2005 DTS Designer Components. The Designer Components distribution replaces the components that get uninstalled when you upgrade your last instance of SQL Server 2000. If you want to upgrade all your SQL Server 2000 instances, this is the best and only option for recovering the DTS designer.

Is anybody heard of this 2005 DTS Designer component?

Where to download? How it works? Any experience to will be appreciated.

Thanks,

Charley

Some info here-

DTS2000
(http://wiki.sqlis.com/default.aspx/SQLISWiki/DTS2000.html)

|||

Thanks so much.

Charley

Microsoft Reporting Services - Error - Expects Parameter - Stored Procedure

Solution:
This happens to me quite a bit...its because the designer removes the
code that defines what
values are passed to your stored procedure.
You have to select the report you're working on > Right-Click 'Code' >
Locate the <Query> XML tag...and you'll have to re-define the
<QueryParameters>.
<Query>
<DataSourceName>GPS</DataSourceName>
<CommandType>StoredProcedure</CommandType>
<CommandText>spLRGetLeadRotationSummary</CommandText>
<QueryParameters>
<QueryParameter Name="@.StartDate">
<Value>=Parameters!StartDate.Value</Value>
</QueryParameter>
<QueryParameter Name="@.EndDate">
<Value>=Parameters!EndDate.Value</Value>
</QueryParameter>
<QueryParameter Name="@.RegionID">
<Value>=Parameters!RegionID.Value</Value>
</QueryParameter>
</QueryParameters>
</Query>You can also do this by clicking on the ..., parameters tab. Modifying the
xml is dangerous. Although if you have a lot of query parameters and RS
keeps losing it then I have sometimes saved the section off so I could copy
it back in.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<petejk@.gmail.com> wrote in message
news:1135124852.986963.63390@.f14g2000cwb.googlegroups.com...
> Solution:
> This happens to me quite a bit...its because the designer removes the
> code that defines what
> values are passed to your stored procedure.
> You have to select the report you're working on > Right-Click 'Code' >
> Locate the <Query> XML tag...and you'll have to re-define the
> <QueryParameters>.
>
> <Query>
> <DataSourceName>GPS</DataSourceName>
> <CommandType>StoredProcedure</CommandType>
> <CommandText>spLRGetLeadRotationSummary</CommandText>
> <QueryParameters>
> <QueryParameter Name="@.StartDate">
> <Value>=Parameters!StartDate.Value</Value>
> </QueryParameter>
> <QueryParameter Name="@.EndDate">
> <Value>=Parameters!EndDate.Value</Value>
> </QueryParameter>
> <QueryParameter Name="@.RegionID">
> <Value>=Parameters!RegionID.Value</Value>
> </QueryParameter>
> </QueryParameters>
> </Query>
>

Microsoft CRM Picklist Fields in Reports

Hi,
I have experience with Crystal Report Designer and Microsoft CRM. I am now
writing reports in SQL Reporting Services. In Crystal when you add a
picklist field to a report you are able to pick a field called
CaseTypeCodeName and it automatically associates the IncidentBase table to
the StringMap table so that the values for the picklist field automatically
show up.
I do not see that feature in SQL Reporting Services. What I am wondering is
how did people get around this? Do I need a special SQL query to pull this
information?
Thanks!!Yeah, just create a UDF that pulls the appropriate StringMap value.
"Amy" <Amy@.discussions.microsoft.com> wrote in message
news:F6800BE4-2DA9-4803-88D6-4DBEEB170502@.microsoft.com...
> Hi,
> I have experience with Crystal Report Designer and Microsoft CRM. I am
now
> writing reports in SQL Reporting Services. In Crystal when you add a
> picklist field to a report you are able to pick a field called
> CaseTypeCodeName and it automatically associates the IncidentBase table to
> the StringMap table so that the values for the picklist field
automatically
> show up.
> I do not see that feature in SQL Reporting Services. What I am wondering
is
> how did people get around this? Do I need a special SQL query to pull
this
> information?
> Thanks!!