Item not linked to dataset, and "table1" issue

Hi--

I have a report project in VS (2003). I have a report in that project that was working properly. I copied objects from that report to a new one and created a new dataset for the new report (under it's Data tab). Though both datasets (for each of the reports) seem healthy, i.e., they produce data when run, I am now experiencing the following problems:

1. In both reports, the datasets seem to be unlinked, somehow. I know this by right clicking on a field of the report, going to expressions, then selecting the Fields node. Instead of listing fields, as used to be the case, it now says "Report item not linked to a dataset."

2. If I attempt to preview either of the reports, I get an error that reads, "The table 'table1' refers to an invalid dataset name 'MedMgmt.' MedMgmt is the dataset name of the first report. I changed it to another name, but I still get the same message.

I have clicked and right-clicked everywhere and have not found a way to re-link the dataset to the report. Why Reporting Services can't figure out that the dataset in the report's Data tab is the dataset to link to is a point of deep annoyance, but whatever... If anyone can please help me solve these problems, I would be very grateful! Thank you!

I have exactly the same problem. Only way around it (for me) so far has been to build the report all over and let the wizard link it, then copy the elements 1 by 1 from original... real pain...

There's GOT to be a better way?

|||

I think i know what it is. What is this object you are looking to link? If its a table, List, or Matrix : Right click the object (make sure the whole object is selected and click properties. if properties slides out Scroll down to "Dataset Name", there should be a drop down which all the datasets in your report. Select the one you are grabbing you attributes from. The reason your getting that error is, the object is linked to dataset names from your other report (since you copied them over). So you need to change the dataset names for each object. This is why it shows the name of your dataset from your other report.

IF the properties box opens up for the table/matrix/list , then you should see (3 textboxes down) "Dataset Name". if its empty or has something in it...i would click the dropdown anyways, and make sure the right dataset it selected.

I hope this helps!

Item not linked to dataset, and "table1" issue

Hi--

I have a report project in VS (2003). I have a report in that project that was working properly. I copied objects from that report to a new one and created a new dataset for the new report (under it's Data tab). Though both datasets (for each of the reports) seem healthy, i.e., they produce data when run, I am now experiencing the following problems:

1. In both reports, the datasets seem to be unlinked, somehow. I know this by right clicking on a field of the report, going to expressions, then selecting the Fields node. Instead of listing fields, as used to be the case, it now says "Report item not linked to a dataset."

2. If I attempt to preview either of the reports, I get an error that reads, "The table 'table1' refers to an invalid dataset name 'MedMgmt.' MedMgmt is the dataset name of the first report. I changed it to another name, but I still get the same message.

I have clicked and right-clicked everywhere and have not found a way to re-link the dataset to the report. Why Reporting Services can't figure out that the dataset in the report's Data tab is the dataset to link to is a point of deep annoyance, but whatever... If anyone can please help me solve these problems, I would be very grateful! Thank you!

I have exactly the same problem. Only way around it (for me) so far has been to build the report all over and let the wizard link it, then copy the elements 1 by 1 from original... real pain...

There's GOT to be a better way?

|||

I think i know what it is. What is this object you are looking to link? If its a table, List, or Matrix : Right click the object (make sure the whole object is selected and click properties. if properties slides out Scroll down to "Dataset Name", there should be a drop down which all the datasets in your report. Select the one you are grabbing you attributes from. The reason your getting that error is, the object is linked to dataset names from your other report (since you copied them over). So you need to change the dataset names for each object. This is why it shows the name of your dataset from your other report.

IF the properties box opens up for the table/matrix/list , then you should see (3 textboxes down) "Dataset Name". if its empty or has something in it...i would click the dropdown anyways, and make sure the right dataset it selected.

I hope this helps!

Issue while using Transfer Sql Server Objects tasks

Hi
I am trying to use Transfer SQL Server Object task to transfer various
DB objects from a Source DB to a newly created Destination DB. The
Destination DB is blank before this attempted transfer.
Now our source Db contains various SPs and views which internally
reference other SPs/Views of the same DB (source DB). For example we
have 2 SPs - SP1 and SP2. Now SP1 internally executes SP2. Whie using
transfer objects task, if we try to transfer all SPs only, we get an
error saying that SP2 does not exist while creating SP1. It seems SSIS
compiles objects while transfering them. We tried to set the
DelayValidation property of the entire package as well as the task to
True, but this didnt help either.
It would be great if someone could suggest some mechanism to prevent
compilation of objects, or any other method using which we can avoid
the problem that we are facing.
Thanks
Regards,
Piyush
I would redirect any failure to a logging table or other, or even ignore
errors.
On 1st pass sp1 will fail, but sp2 should still be created, correct? Then
perform a second pass which will cause sp2 to fail because already exists,
however sp1 will compile and create fine since dependency now exists...
You will get a quicker response if you post to dts group for ssis questions.
good luck.
ChrisB MCDBA
MSSQLConsulting.com
"whirlwnd" wrote:

> Hi
> I am trying to use Transfer SQL Server Object task to transfer various
> DB objects from a Source DB to a newly created Destination DB. The
> Destination DB is blank before this attempted transfer.
> Now our source Db contains various SPs and views which internally
> reference other SPs/Views of the same DB (source DB). For example we
> have 2 SPs - SP1 and SP2. Now SP1 internally executes SP2. Whie using
> transfer objects task, if we try to transfer all SPs only, we get an
> error saying that SP2 does not exist while creating SP1. It seems SSIS
> compiles objects while transfering them. We tried to set the
> DelayValidation property of the entire package as well as the task to
> True, but this didnt help either.
> It would be great if someone could suggest some mechanism to prevent
> compilation of objects, or any other method using which we can avoid
> the problem that we are facing.
> Thanks
> Regards,
> Piyush
>