Comments
Sort by recent activity
Hi Bart,
I appreciate your insight and now understand some of your concerns / problems involved.
I agree, DD will not "saturate" the market. I agree, at that price DD could (and will certainly at some point) include Intellisense.
I do expect, that MS will change the direction of DD a bit, making the project model the standard model for all VS Versions since the current situation (DB Projects that are not compatible) is crazy.
I disagree at the moment as far as the ease of implementation is concerned, since the design time validation of DD is based on a complete local SQL Server instance of the project. The local design time DB would serve fine for your meta data as long as cross server is not required.
However, the local design time DB will probably be dropped by DD in a few years.
Where would one need it? When creating objects, especially SP's and Views.
Alle / comments
Hi Bart,
I appreciate your insight and now understand some of your concerns / problems involved.
I agree, DD will not "saturate" the market. I agree, at that price DD could (and will certainly at s...
I understand that the scripts and behavior of the DBPro files are different than the same for the generic database projects.
It is true, that DataDude database projects are not the same or compatible to the standard database projects. The T-SQL and scripting of the same is however of course identical.
It's disappointing because the lack of support for VS 2005 was not "advertised" by Red Gate until shortly before the release of SQL Prompt 3 (and after many of us had ordered based on the only available description of Prompt 2 which supported VS all the time).
Now for about the last half year RG has been talking about including VS support, finally 3.5 is released which "includes support for VS 2005" and after the release I again find an EXCEPT for the ....... Version (which happens to be the version I and others have).
Not very nice.
Alle / comments
I understand that the scripts and behavior of the DBPro files are different than the same for the generic database projects.
It is true, that DataDude database projects are not the same or com...
@ Granted
Reading more I've found that I'm trying to work with an unsupported version of VS, Visual Studio Team Edition for Database Professionals.
Sorry. RTFM!
Could you point me at the FM that states this? Doesn't make that much difference, but it seems silly. Data Dude is actually only an add in to VS 2005, just as SQL Prompt is.
I bought on the premise that VS 2005 would be supported, period. Up to now quite disappointing.
Alle / comments
@ Granted
Reading more I've found that I'm trying to work with an unsupported version of VS, Visual Studio Team Edition for Database Professionals.
Sorry. RTFM!
Could you point me at the FM that ...
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 / comments
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 surpri...
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. / comments
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 l...
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 / comments
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...
Hi,
in some of the replies you indicate English System (I assume OS) and on others it would seem that an English SQL Server installation is meant.
How about someone that knows, being very clear on what is required for what.
I have English VS2005 and English SQL Server 2005 and German OS (WXP Pro SP2).
1. SQL Prompt DOES work with SQL Server.
2. SQL Prompt DOES NOT work with VS 2005 (in Database Project in .sql file ;-)).
Be glad to recieve some clarity.
Thanks.
Alle / comments
Hi,
in some of the replies you indicate English System (I assume OS) and on others it would seem that an English SQL Server installation is meant.
How about someone that knows, being very clear on ...