Settings and activity

12 results found

  1. 14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stephen Anslow supported this idea  · 
  2. 215 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    36 comments  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stephen Anslow commented  · 

    Thanks, Marty, for taking the time to expand on your comments. Being the only DB-centric developer/accidental DBA and having been bitten by the current VS DB Project required way of working, I was hoping there was a clear this-vs.-that kind of checklist, for want of a better word, that would help bridge the gaps in my experience and enable me to make a more educated decision over either wait for VS-next and embrace it, or ignore its features and attempt to use SQL Connect, a tool, again, one has no experience of. Thanks again.

    I hope Red Gate can put together a feature/practice summary/white paper that clearly sets out the comparable features of RG Tools vs. VS-Next w/ SSDT so decision makers have what they need... Doubtless someone at RG must have given considerable thought to come up with SQL Connect and SSC in their current forms, knowing that VS-Next w/ SSDT was rapidly approaching...

    An error occurred while saving the comment
    Stephen Anslow commented  · 

    @Marty: tapping your 3+ years of knowledge, how would you compare the *upcoming VS release*, including all the SSDT functionality with the SQL Connect/SSC offerings from Red Gate. Which features IYE are incompatible and which are missing from the other? Which are roadblocks to enjoying SSDT? Which hinder RG Project/SSC usage?

    I've no interest in the CURRENT version of VS vs. RG, only interested in finally being able to, at the very least, enjoy offline DB modifications with full impact analysis within VS-next.

    Thanks in advance for sharing your understanding, provided you have time, naturally. Regular work = top priority.

    Stephen Anslow supported this idea  · 
    An error occurred while saving the comment
    Stephen Anslow commented  · 

    Looking at the SSDT Videos (Juneau) via the connect surveys (https://connect.microsoft.com/BusinessPlatform/Surveys), SQL Connect and SQL Source Control had better get in on" VS2010 as the ONE-STOP-SHOP" that Microsoft is determinedly heading towards making a reality.

    I've been a supporter of Red Gate tools for 6+ years and find them indispensable. HOWEVER, SSDT integration into VS2010 is VERY compelling and, as a SQL Source Control user (SVN, not TFS), I absolutely MUST have integration of SSC into VS2010, cohabiting with SSDT in every possible way.

    RED GATE NEEDS TO PUBLISH A ROADMAP THAT ASSURES CURRENT AND PROSPECTIVE CUSTOMERS THAT RG TOOLS WILL BE FULLY INTEGRATED INTO VS2010 FOR SQL 2012. At the very least Red Gate needs to publish illustrated technical papers on the features of VS2010 and SSDT and the integration points SUPPORTED and PLANNED, with dates!

    Your public needs to hear from you, Red Gate, with FAR more than the scant "Roadmap" bullet points on the main site. (http://www.red-gate.com/our-company/about/news/ ==> Roadmap)

  3. 56 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  SQL Prompt » Smart rename  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’re going to be reviewing this over the next couple of months, which would be released via the SQL Prompt for Teams EAP (get in touch if you want to know more).

    In the meantime please add any other information that you think would be useful.

    An error occurred while saving the comment
    Stephen Anslow commented  · 

    As there's no bulk rename, I can't quantify that. The pain of changing over 500 columns piecemeal is not something I wish to inflict upon myself.

    Quantification on the single-column front comes down to "how long is a piece of string?" and varies from month to month from zero, to a few columns - mostly zeros.

    Like I said, as there's no bulk rename, i.e., rename every column in a given table, how can I give you a number? If it were present, likely there would be several timebox projects carving up the renames from light impact first through pervasive, over the course of at least a year.

    Apologies for a somewhat woolly answer...

    Stephen Anslow supported this idea  · 
  4. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Source Control » History/Log  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stephen Anslow shared this idea  · 
  5. 32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stephen Anslow commented  · 

    It looks like this has been included in the 3.0.5.7 version...

    Red Gate, please comment...

    Stephen Anslow shared this idea  · 
  6. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  SQL Prompt » Intellisense  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Prompt » Smart rename  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stephen Anslow shared this idea  · 
  8. 189 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 77 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SQL Search » Graphical User Interface  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stephen Anslow commented  · 

    If we can't have multiple searches, allow us, for any number of found objects, to "Open in reference pane" so the highlighting of the finds is retained and we can scroll through (with the proposed Prev-Next buttons) while we look at associated objects either in the main lower pane or other "reference" panes. I can see this being useful with SPs that use nested SPs and/or UDFs, similar for UDFs that call additional UDFs. Sadly SSMS doesn't have the "highlight all occurences" feature that so many useful text editors provide; this feature would be a beneficial substitute, IMO.

    Stephen Anslow supported this idea  · 
  10. 336 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  SQL Search  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stephen Anslow shared this idea  · 
  12. 89 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’re currently not planning to support this for v1. Would you be ok to remove the $id$ keyword for now?

    We’ll have to see how many votes this suggestion gets…

    Internal reference number: SOC-113