October 11, 2010 at 10:12 am
Are there any workarounds to the issue with Report Builder in SQL 2005 which means that a report model and report itself have to be recreated / regenerated if an underlying view is changed? Advice welcome!
October 12, 2010 at 2:41 am
I would love to hear any real world implementations of report models. As far as I've seen them, they're unusable if there's going to be any changes in the database schema, or the database will ever be recreated by scripts (not a simple backup/restore).
I started a contract 6 months ago taking over from another report designer that used them, and none of them worked. I wasn't able to fully match the errors I was getting from the designer. I had to reverse-engineer it by capturing a trace on the SQL server and working out the names of the tables and fields it was trying to find, and replacing everything in the reports with T-SQL. It has been smooth sailing since.
I did think about writing some kind of tool to go through and adjust everything in the XML, but it's a little beyond my capabilities, and in the end wasn't necessary. It has since been redone in 2008 R2 anyway; I wonder if those new report bits have the same problem?
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply