You’re offline. This is a read only version of the page.
I realize both editions are fully supported but I am interested in hearing from your experience whether there are currently any caveats for using SQL 2012 in a brand new deployment.
*This post is locked for comments
+More informatuion on this in corelation to Dynamics CRM
Microsoft Dynamics CRM and SQL Server 2012 - Better Togetherblogs.msdn.com/.../microsoft-dynamics-crm-and-sql-server-2012-better-together.aspx
Thanks,
With regard to the top rated features of SQL 2012 you can refer to this article. It has always been most helpful for me:
blogs.technet.com/.../my-top-5-sql-server-2012-features-by-aaron-bertrand-guest-blogger.aspx
A few of disadvantages as I see are these:
2012 might be more expensive to implement depending on version/hardware
Not all 3rd party software vendors have confirmed official support for 2012 as a backend database (check into what software they want to run on it)
2012 is relatively new - many organisations (such as the one I work for) avoid implementing new software until SP1 has been released.
Support for Microsoft Dynamics CRM with Microsoft SQL Server 2012:
support.microsoft.com/.../2686619
SQL Server 2012 or 2008 for a new CRM 2011 UR12 On-premise Deployment?: technet.microsoft.com/.../jj822357.aspx
If you plan on doing any custom reports with 2012 you will still need to use BIDS 2008 if you need to use the Report Authoring Extension to access the FetchXML capabilities.
Also make sure you download and install off the latest media, if you have an earlier version, the install will give you problems.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (