How can we help you today? How can we help you today?

SQL Prompt 3 and Visual Studio Team 4 Database Professionals

Hallo,

with your connections to Microsoft I'm sure you are aware that Visual Studio Team System will be expanded with an edition for Database Professionals in the next months. This product is designed for working completely in T-SQL Scripts and there is no MS SQL intellisense for this work.

Up to now (SQL Prompt 2) your product only works for Visual Studio in query windows that are opened from the server explorer. It does not work for windows out of the database project / solution exporer.

Will SQL Prompt 3 offer this functionality?
ajk-eis
0

Comments

12 comments

  • Tom Harris
    Hi there,

    SQL Prompt 3 will not be offering this integration in the first release. SQL Prompt 3 will only be supporting Query Analyzer and SQL Server Management Studio.

    Support for other editors will be looked at for the next version.

    Thanks,

    Tom Harris

    Red Gate Software
    Tom Harris
    0
  • ajk-eis
    Hi Tom,

    That is certainly disappointing, as the description of the product says
    SQL Prompt works with Microsoft Query Analyzer, SQL Server 2005 Management Studio, Visual Studio 2005, Visual Studio .NET 2003 ...

    Since the files being worked in the editor in VSTS4DBP are also files with the extension .sql which are listed in the SQL Prompt Properties under VS 2003 / 2005. Additionally these file, in the case of VSTS4DBP are being editied in a SQLCMD window (exactly the same as SQL Server Management Studio). I would surely have expected support at least here. This doesn't work with VS 2003 or 2005 either in .sql files, except as stated in the original post out of the server explorer.

    I find your statements in the description of the product (without the qualification of "partial support" somewhat misleading. :?

    Alle
    ajk-eis
    0
  • Tom Harris
    Hi there,

    SQL Prompt 2 did support more editors. However, we never planned to include support for anything other than QA and SSMS in SQL Prompt 3. I'm sorry if this is something of a disappointment, but we had to draw the feature line somewhere. We will look into support for more editors in the next version.

    Regards,

    Tom
    Tom Harris
    0
  • ajk-eis
    Tom Harris wrote:
    SQL Prompt 2 did support more editors. However, we never planned to include support for anything other than QA and SSMS in SQL Prompt 3.

    In that Case SQL Prompt has lost at least 50% of it's value and you are STILL advertising (http://www.red-gate.com/products/SQL_Prompt/index.htm) with all of the editors.

    If it wasn't at the introductory offer price, I would certainly revoke my order now . Even at that price, I will consider backing out. Visual Studio support is a basic support at least at the level it was with SQL Prompt 2.

    Have all of your preorder customers been advised of this cutback in functionality? I know I wasn't.
    ajk-eis
    0
  • Tilman
    Hi,

    I agree we did not handle this situation very well. We should have told you earlier that we are not going to support VS in SQL Prompt 3. I do apologise for that. If you want to revoke your pre-order because of this, please get in contact with sales (sales@red-gate.com). I do believe, however, that the improved functionality still makes it a very useful product.

    Basically, what happened was, we did a survey asking, amongst other things, what editor people used, and VS 2003 and 2005 together accounted for approximately 3%. Query Analyzer and Management Studio on the other hand accounted for over 90%. So it seemed a good idea to us to concentrate on those two editors and to improve the product in other areas.

    Maybe I should also mention here that, for the above reasons, we do not support EditPlus nor UltraEdit nor Enterprise Manager in SQL Prompt 3.

    Regards,

    Tilman
    Tilman
    0
  • MikeGuerrieri
    Hello,

    I agree with ajk-eis that this is a very unwelcome surprise. Our development team does the vast majority of their SQL development with Visual Studio 2003 and SQL Prompt 2 works with this product. All of our SQL scripts are in database projects and checked into source control. Using Visual Studio allows our developers to use 1 IDE to both edit our scripts and manage them in source control.

    I can't recall any communication that indicated that this functionality would be removed from version 3. Since we have not yet migrated to SQL Server 2005 this means that the only tool in our shop that is supported by SQL Prompt will be Query Analyzer which is used in our shop mainly for ad-hoc queries and analysis.

    I'm sorry to say that this customer will be calling your sales team to revoke my subscription.
    MikeGuerrieri
    0
  • MikeGuerrieri
    Hello,

    So I called your sales team to revoke my subscription and was offered a bundled package wich includes SQL Refactor, SQL Dependancy Tracker, and (now useless to me) SQL Prompt 3. This bundle was offered at no additional cost. The Refactor and Dependancy Tracker tools seem like they may be very useful so I decided to take the bundle and give them a try. The Red-Gate representative indicated that this would be at 'no risk' meaning that if I wasn't satisfied that I could still get a refund.

    Even though I'm very disapointed at the turn that SQL Prompt has taken, I think that the folks at Red-Gate are making a sincere effort to try and make it up to those that have been adversely affected by their decisions regarding SQL Prompt.
    MikeGuerrieri
    0
  • ajk-eis
    Tilman wrote:
    Basically, what happened was, we did a survey asking, amongst other things, what editor people used, and VS 2003 and 2005 together accounted for approximately 3%.

    Were you surprised? This is a typical case of misused statistics. If I ask blind people how many of them can see I will get 0%.

    Your survey was asked of a group that is almost 100% DBA's (probably close to the 90% you qoute above). I, as a developerment manager was not even aware of your product until I stumbled across a blog mentioning it.

    I would claim that my group (developers) has a mucher higher need / use for the tool than DBA's (since we are not as aware of the DB schema as a DBA), but weren't aware of it's existance.

    Anyway, that's the way it is and it certainly won't change shortly. I'll let you know what I decide (at sales).

    Alle
    ajk-eis
    0
  • Tilman
    Hi Alle,
    Were you surprised?

    Yes.
    Your survey was asked of a group that is almost 100% DBA's (probably close to the 90% you qoute above).

    We asked people who responded to the survey what they considered their job to be. 67% of people claimed they were software developers/engineers, or software architects (53% software developers/engineers) as opposed to 24% who claimed to be DBAs.

    However, we have already started looking into integrating SQL Prompt 3 into VS 2005 for an upcoming release. I'm afraid, there will be no support for VS 2003, though.

    Regards,

    Tilman
    Tilman
    0
  • schaitel
    I don't know what all the big deal is. I don't know any SQL Developers who uses Visual Studio for SQL development. We all use Enterprise Manager, Query Analyzer or SQL Management Studio. I think you folks who use VS are a minority. I don't think you should give Red-Gate a hard time about it.
    schaitel
    0
  • Matthew.Wilkerson
    Our development team does the vast majority of their SQL development with Visual Studio 2003 and SQL Prompt 2 works with this product. All of our SQL scripts are in database projects and checked into source control. Using Visual Studio allows our developers to use 1 IDE to both edit our scripts and manage them in source control.

    If this helps any, you can use database projects in SQL Management Studio (which works with versions 2 and 3) to edit scripts and manage them in source control.
    Since we have not yet migrated to SQL Server 2005 this means that the only tool in our shop that is supported by SQL Prompt will be Query Analyzer which is used in our shop mainly for ad-hoc queries and analysis.

    You can use the SQL Management Studio IDE with SQL 2000 databases without migrating to SQL 2005 yet as well. That's what we are doing until we migrate to SQL 2005. In doing so we will be able to continue to use SQL Prompt, version 2 or 3.
    Matthew.Wilkerson
    0
  • MikeONeill
    I started a new thread cos I didn't see this one .

    I agree with most of the above , I too was expecting VS2005 support as just like PromptSQL and SQLPrompt 2 .And wasn't aware it was specifically excluded.

    Its a bit late to withdraw now , I bought way back in Oct and have been waiting with baited breath , what see so far is excellent and I wouldn't really like to be without it , I have used all 3 versions and "Love it To Bits"

    I hope the support for VS 2005 comes before our 1 year support free upgrade runs out . I Assume by the way that that runs from Activation(??)

    I appreciate the commentary around the use of QA and SQL mgt Studio but I am one who likes to work in one IDE where possible , . I do a lot of work on a "limp" lap top and wnything that preserves resources like one IDE is a bonus
    MikeONeill
    0

Add comment

Please sign in to leave a comment.