November 2, 2016 at 2:36 pm
I've been using SSMS and Profiler 2012 with our SQL 2008 R2 data fine. All I ever have to do with Profiler is log in and run. Now that our dbs have been migrated to SQL 2014, I get "At least one event must be selected" but I have "Show All Events" checked like normal. The only way it runs if I manually select each event. It also doesn't show the same information that it used to on 2008 so I can see the sql queries being run.
What am I missing here? Do I have to have SSMS 2014 now?
November 2, 2016 at 3:17 pm
Have you looked at using extended events? Profiler has been deprecated for running traces. (Although, you didn't specify that you were running a trace.)
Drew
J. Drew Allen
Business Intelligence Analyst
Philadelphia, PA
November 2, 2016 at 5:21 pm
Yes, you should upgrade to SSMS 2014. Backwards compatibility is largely ensured within SSMS, so 2012 will work with 2008R2, 2008, 2005 and 2000. However, forward compatibility is absolutely not ensured. How can it be. They have no idea what they're releasing in 2014 when they make 2012, and they don't (as of 2012) update SSMS independently so that it could work with both equally well. Microsoft has changed the SSMS release process as of 2016, so it's possible that your SSMS will be forward compatible when 2018 comes out (although it will mean upgrading SSMS to whatever version is current for that to work).
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply