Are the posted questions getting worse?

  • Yes, still WS2003/SQL2008. Causes some issues. Upgrade in discussion now.

  • Thom A - Thursday, October 12, 2017 6:24 AM

    That's a handy little node Microsoft have added to SSMS (17.3). They've put "XE profiler" at the bottom of the objects for a serve. Effectively does the job of profiler via Extended Events (but, obviously isn't using profiler). A nice little feature, and much easier to use than having to create an Extended Events for something you don't already have set up (and don't need long term so remove afterwards).

    It is nice but there are a few bugs, which is a pity because I don't believe it was a major technical challenge to add it.

  • BrainDonor - Friday, October 13, 2017 12:56 AM

    Thom A - Thursday, October 12, 2017 6:24 AM

    That's a handy little node Microsoft have added to SSMS (17.3). They've put "XE profiler" at the bottom of the objects for a serve. Effectively does the job of profiler via Extended Events (but, obviously isn't using profiler). A nice little feature, and much easier to use than having to create an Extended Events for something you don't already have set up (and don't need long term so remove afterwards).

    It is nice but there are a few bugs, which is a pity because I don't believe it was a major technical challenge to add it.

    Mmm, after a bit more investigation, noticed that there is no option to filter on Username, only nt_username. As we have SQL Authentication enabled, not that helpful... D'oh!

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

  • Thom A - Thursday, October 12, 2017 6:24 AM

    That's a handy little node Microsoft have added to SSMS (17.3). They've put "XE profiler" at the bottom of the objects for a serve. Effectively does the job of profiler via Extended Events (but, obviously isn't using profiler). A nice little feature, and much easier to use than having to create an Extended Events for something you don't already have set up (and don't need long term so remove afterwards).

    Very interesting - thanks Thom!

    β€œWrite the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw

    For fast, accurate and documented assistance in answering your questions, please read this article.
    Understanding and using APPLY, (I) and (II) Paul White
    Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden

  • BrainDonor - Friday, October 13, 2017 12:56 AM

    Thom A - Thursday, October 12, 2017 6:24 AM

    That's a handy little node Microsoft have added to SSMS (17.3). They've put "XE profiler" at the bottom of the objects for a serve. Effectively does the job of profiler via Extended Events (but, obviously isn't using profiler). A nice little feature, and much easier to use than having to create an Extended Events for something you don't already have set up (and don't need long term so remove afterwards).

    It is nice but there are a few bugs, which is a pity because I don't believe it was a major technical challenge to add it.

    There are a few other gotchas with SSMS 17.3 - particularly with its now-non-support of SQL2005's Agent tasks (I know, I know...)  So don't get rid of SSMS2014 just yet!

    Thomas Rushton
    blog: https://thelonedba.wordpress.com

  • ThomasRushton - Friday, October 13, 2017 2:27 AM

    There are a few other gotchas with SSMS 17.3 - particularly with its now-non-support of SQL2005's Agent tasks (I know, I know...)  So don't get rid of SSMS2014 just yet!

    True, but at least the product does say it only supports currently supported versions of SQL Server (2008-2017) πŸ˜‰

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

  • Thom A - Friday, October 13, 2017 4:42 AM

    ThomasRushton - Friday, October 13, 2017 2:27 AM

    There are a few other gotchas with SSMS 17.3 - particularly with its now-non-support of SQL2005's Agent tasks (I know, I know...)  So don't get rid of SSMS2014 just yet!

    True, but at least the product does say it only supports currently supported versions of SQL Server (2008-2017) πŸ˜‰

    Also true, and I knew that before I went in.  "But it was working before"...  :laugh:

    Thomas Rushton
    blog: https://thelonedba.wordpress.com

  • ThomasRushton - Friday, October 13, 2017 2:27 AM

    BrainDonor - Friday, October 13, 2017 12:56 AM

    Thom A - Thursday, October 12, 2017 6:24 AM

    That's a handy little node Microsoft have added to SSMS (17.3). They've put "XE profiler" at the bottom of the objects for a serve. Effectively does the job of profiler via Extended Events (but, obviously isn't using profiler). A nice little feature, and much easier to use than having to create an Extended Events for something you don't already have set up (and don't need long term so remove afterwards).

    It is nice but there are a few bugs, which is a pity because I don't believe it was a major technical challenge to add it.

    There are a few other gotchas with SSMS 17.3 - particularly with its now-non-support of SQL2005's Agent tasks (I know, I know...)  So don't get rid of SSMS2014 just yet!

    AFAIK SSMS 2016 works with 2005, I don't have any 2005 servers around to check though, so...

  • ThomasRushton - Friday, October 13, 2017 5:22 AM

    Thom A - Friday, October 13, 2017 4:42 AM

    ThomasRushton - Friday, October 13, 2017 2:27 AM

    There are a few other gotchas with SSMS 17.3 - particularly with its now-non-support of SQL2005's Agent tasks (I know, I know...)  So don't get rid of SSMS2014 just yet!

    True, but at least the product does say it only supports currently supported versions of SQL Server (2008-2017) πŸ˜‰

    Also true, and I knew that before I went in.  "But it was working before"...  :laugh:

    If anyone knows, I'm curious if SQL 2017 will restore a SQL 2005 database from backup.

  • Jack Corbett - Friday, October 13, 2017 6:48 AM

    ThomasRushton - Friday, October 13, 2017 2:27 AM

    BrainDonor - Friday, October 13, 2017 12:56 AM

    Thom A - Thursday, October 12, 2017 6:24 AM

    That's a handy little node Microsoft have added to SSMS (17.3). They've put "XE profiler" at the bottom of the objects for a serve. Effectively does the job of profiler via Extended Events (but, obviously isn't using profiler). A nice little feature, and much easier to use than having to create an Extended Events for something you don't already have set up (and don't need long term so remove afterwards).

    It is nice but there are a few bugs, which is a pity because I don't believe it was a major technical challenge to add it.

    There are a few other gotchas with SSMS 17.3 - particularly with its now-non-support of SQL2005's Agent tasks (I know, I know...)  So don't get rid of SSMS2014 just yet!

    AFAIK SSMS 2016 works with 2005, I don't have any 2005 servers around to check though, so...

    SSMS 2016 does work with SQL 2005.  I still have one I have to support.

  • Ed Wagner - Friday, October 13, 2017 6:56 AM

    Jack Corbett - Friday, October 13, 2017 6:48 AM

    ThomasRushton - Friday, October 13, 2017 2:27 AM

    BrainDonor - Friday, October 13, 2017 12:56 AM

    Thom A - Thursday, October 12, 2017 6:24 AM

    That's a handy little node Microsoft have added to SSMS (17.3). They've put "XE profiler" at the bottom of the objects for a serve. Effectively does the job of profiler via Extended Events (but, obviously isn't using profiler). A nice little feature, and much easier to use than having to create an Extended Events for something you don't already have set up (and don't need long term so remove afterwards).

    It is nice but there are a few bugs, which is a pity because I don't believe it was a major technical challenge to add it.

    There are a few other gotchas with SSMS 17.3 - particularly with its now-non-support of SQL2005's Agent tasks (I know, I know...)  So don't get rid of SSMS2014 just yet!

    AFAIK SSMS 2016 works with 2005, I don't have any 2005 servers around to check though, so...

    SSMS 2016 does work with SQL 2005.  I still have one I have to support.

    SSMS 2017 is working fine with 2005, 2008, 2008 R2, 2012, 2014, and 20126.  Yes, I still have to support all of them!

    Michael L John
    If you assassinate a DBA, would you pull a trigger?
    To properly post on a forum:
    http://www.sqlservercentral.com/articles/61537/

  • Michael L John - Friday, October 13, 2017 8:56 AM

    SSMS 2017 is working fine with 2005, 2008, 2008 R2, 2012, 2014, and 20126.  Yes, I still have to support all of them!

    Timewarp again?
    And lucky you, having all of those to support :ermm:

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Michael L John - Friday, October 13, 2017 8:56 AM

    SSMS 2017 is working fine with 2005, 2008, 2008 R2, 2012, 2014, and 2016.  Yes, I still have to support all of them!

    and 2017 coming soon, I'm sure

  • Phil Parkin - Friday, October 13, 2017 9:10 AM

    Michael L John - Friday, October 13, 2017 8:56 AM

    SSMS 2017 is working fine with 2005, 2008, 2008 R2, 2012, 2014, and 20126.  Yes, I still have to support all of them!

    Timewarp again?
    And lucky you, having all of those to support :ermm:

    Times like this I'm glad it's just 2012 and 2008 here. πŸ˜€

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

  • Thom A - Friday, October 13, 2017 9:20 AM

    Phil Parkin - Friday, October 13, 2017 9:10 AM

    Michael L John - Friday, October 13, 2017 8:56 AM

    SSMS 2017 is working fine with 2005, 2008, 2008 R2, 2012, 2014, and 20126.  Yes, I still have to support all of them!

    Timewarp again?
    And lucky you, having all of those to support :ermm:

    Times like this I'm glad it's just 2012 and 2008 here. πŸ˜€

    Even that would frustrate me. SSIS changed so much in 2012, I'd hate to have to deal with it in 2008 again.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

Viewing 15 posts - 60,106 through 60,120 (of 66,549 total)

You must be logged in to reply to this topic. Login to reply