SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


[rsErrorReadingDataSetField] The dataset contains a definition for the Field. The data extension...


[rsErrorReadingDataSetField] The dataset contains a definition for the Field. The data extension returned an error during reading the field. There is no data...

Author
Message
Abhishek Chaturvedi
Abhishek Chaturvedi
SSC Veteran
SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)

Group: General Forum Members
Points: 230 Visits: 283
Hi,
I am trying to create a report which takes the instance_name and Database_name as input parameters and displays the table_name, row_count, column_count, size of the table. I am using the below query to populate the report.


CREATE TABLE #temp (
table_name varchar(50) ,
row_count INT,
reserved_size VARCHAR(50),
data_size VARCHAR(50),
index_size VARCHAR(50),
unused_size VARCHAR(50))
SET NOCOUNT ON
INSERT #temp
EXEC sp_msforeachtable 'sp_spaceused "?"'
SELECT a.table_name,
a.row_count,
COUNT(*) AS col_count,
a.data_size
FROM #temp a
INNER JOIN information_schema.columns b
ON a.table_name collate database_default
= b.table_name collate database_default
GROUP BY a.table_name, a.row_count, a.data_size
ORDER BY CAST(REPLACE(a.data_size, 'KB', '') AS integer) DESC
DROP TABLE #temp

However, the report displays the following warnings and the table_name field is blank. All the other columns are displayed correctly.


warning -
Warning 1 [rsMissingFieldInDataSet] The dataset ‘Row_count’ contains a definition for the Field ‘Table_name’. This field is missing from the returned result set from the data source.

Warning 2 [rsErrorReadingDataSetField] The dataset ‘Row_count’ contains a definition for the Field ‘Table_name’. The data extension returned an error during reading the field. There is no data for the field at position 1.


Any help will be appreciated.
Attachments
SSRS_report.JPG (38 views, 43.00 KB)
SSRS_error.JPG (29 views, 45.00 KB)
Abhishek Chaturvedi
Abhishek Chaturvedi
SSC Veteran
SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)

Group: General Forum Members
Points: 230 Visits: 283
This issue was fixed.
bornsql
bornsql
SSC-Enthusiastic
SSC-Enthusiastic (166 reputation)SSC-Enthusiastic (166 reputation)SSC-Enthusiastic (166 reputation)SSC-Enthusiastic (166 reputation)SSC-Enthusiastic (166 reputation)SSC-Enthusiastic (166 reputation)SSC-Enthusiastic (166 reputation)SSC-Enthusiastic (166 reputation)

Group: General Forum Members
Points: 166 Visits: 341
can u please explain how it got fixed ..
smecharrafie
smecharrafie
SSC-Enthusiastic
SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)

Group: General Forum Members
Points: 165 Visits: 189
Please advise how did you get this to work... Im having the same problem but no effective solution so far.

Thanks,
Sam
Abhishek Chaturvedi
Abhishek Chaturvedi
SSC Veteran
SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)

Group: General Forum Members
Points: 230 Visits: 283
Hi,
I found the solution but you won't like the answer Smile.
I created a brand new report with the exact same query and properties and it worked just fine.
smecharrafie
smecharrafie
SSC-Enthusiastic
SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)

Group: General Forum Members
Points: 165 Visits: 189
As per your advise, I created a new report based on the same dataset query and design. Nevertheless, upon attempting to preview the report the warnings would still appear and the values would be missing from the fields relevant to the warnings generated.

What is frustrating is that if I execute the dataset from within the report using query designer then all fields return a value. This means that my underlying dataset sp is in fact intact and the problem is on the report level. I've searched quite a lot for this case but no effective solution is available for this specific scenario. bulding/re-building solution just makes the warnings disappear, but the problem still persists, creating a brand new report based on same design has not resolved it as well.

Any feedback or help is appreciated.


Regards,
Sam
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search