Can't maintain report models against a SQL 2012 database

Question

After upgrading a database to SQL 2012, I can no longer edit my report models against that database.  If I try to edit an existing named query or create a new named query in the DSV, I get this error:

This server version is not supported.  Only servers up to Microsoft SQL Server 2005 are supported.

Answer 1

Hello Dayne,

In SSRS 2012 report model are not longer supported (deprecated), you can still use them, but you can't add new/edit existing report models.

See Deprecated Features in SQL Server Reporting Services in SQL Server 2012:
=> Semantic modeling language (SMDL) report models are deprecated. Although you can you continue to use existing report models as data sources in SQL Server 2012 Reporting Services reports you should consider updating your reports to remove their dependency on report models.

---

Olaf Helper
* cogito ergo sum * errare humanum est * quote erat demonstrandum *
Wenn ich denke, ist das ein Fehler und das beweise ich täglich
Blog Xing

Answer 2

MS really left us out in the cold on this one. They say to use the tabular semantic model. However there are multiple issues with doing that. Report Builder doesn't work very well with it. I've even gone to the PowerView route but then found out that PowerView reports can't be scheduled and can only export to Powerpoint. I have come to the conclusion that I will need to have a machine with SQL 2008 BIDS for maintaining the model.

Answer 3

Hello Dayne,

In SSRS 2012 report model are not longer supported (deprecated), you can still use them, but you can't add new/edit existing report models.

See Deprecated Features in SQL Server Reporting Services in SQL Server 2012:
=> Semantic modeling language (SMDL) report models are deprecated. Although you can you continue to use existing report models as data sources in SQL Server 2012 Reporting Services reports you should consider updating your reports to remove their dependency on report models.

---

I understand that report models are deprecated in SQL 2012 tools, but I can't even edit them using SQL 2008 BIDS now.  If I use SQL 2008 BIDS, and the database I'm querying happens to be 2012, it won't let me edit or add a named query.  It will, however, let me add tables.

Answer 4

MS really left us out in the cold on this one. They say to use the tabular semantic model. However there are multiple issues with doing that. Report Builder doesn't work very well with it. I've even gone to the PowerView route but then found out that PowerView reports can't be scheduled and can only export to Powerpoint. I have come to the conclusion that I will need to have a machine with SQL 2008 BIDS for maintaining the model.

I have to agree.  I'm happy to move to the tabular models, but they just don't seem ready to completely replace report models.  The Report Builder integration is not good - my users have to learn MDX now?  PowerView is a neat tool, but it doesn't have the flexibility to replace Report Builder.  (And I know it's not meant to.)

In the meantime, I have about 100 report models that I can't even manage now if I happened to upgrade the back-end database to SQL 2012.

Answer 5

Hi Dayne,

Sorry for any inconvinece on this issue, could you please submit a feedback at:https://connect.microsoft.com/SQLServer/ . Your feedback is valuable for us to improve our products and increase the level of service provided. We appreciate your understanding.

Lola

---

Please remember to mark the replies as answers if they help.

Answer 6

I'm in a similar situation with SSRS 2005 on the front end and SQL 2008 R2 databases on the backend. For a number of years we had SSRS 2005 on the front end and SQL 2005 on the backend, but the backend database platform has been upgraded to SQL 2008 R2. As a result, I can no longer add or edit Named Queries within the SSRS 2005 Data Source Views. A dialogue comes up now with the followign error- "This server version is not supported. You must have SQL Server 2005 Beta 2 or later". It obviously can't deal with the SQL Server 2008 R2 database gracefully, so is there a work around for this.  We're planning to upgrade/migrate the front end to SSRS 2008 R2 (or SSRS 2012) later this year, but we still need to work with what we have in the meantime.

---

Bill Thacker