Comments
Sort by recent activity
Hi JP,
Thanks for that information, and it's interesting it happened with 3.9 too.
I'll pass on that information to our developers and we'll try to resolve it for the next release.
In the meantime, we may have to contact you again to get more information, would this be ok?
Thankyou for your continuing interest in SQL Prompt 4.0, and I hope to hear more feedback from you soon!
Regards
Chris / comments
Hi JP,
Thanks for that information, and it's interesting it happened with 3.9 too.
I'll pass on that information to our developers and we'll try to resolve it for the next release.
In the meantime,...
Hi,
I'm sorry that you are having these problems. However, I have been unsuccessful at reproducing your issue.
So that we can investigate this further, could you let me know the following information please?
1. Did you already have 3.x installed? if so, which version?
2. What exactly happens when you lose integration? Do you still get the menu in management studio? does prompting happen just without database information? Please describe the symptoms.
3. Is management studio the only application you have open?
Thankyou for taking the time to report this, and thankyou for trying SQL Prompt 4.0 Early Access.
Chris / comments
Hi,
I'm sorry that you are having these problems. However, I have been unsuccessful at reproducing your issue.
So that we can investigate this further, could you let me know the following informati...
Steve,
Put simply, to use SQL Prompt you must have a connection to the database you wish to work on.
We do not support "offline" working where SQL Prompt would continue to provide suggestions even though there was no connection to the database.
The internet connection is only essential if your database resides somewhere remote to your location which needs an internet connection to access that database.
So, as long as your database can be connected via your own LAN, then you do not need an internet connection.
I hope this clears up the confusion :-)
Regards
Chris / comments
Steve,
Put simply, to use SQL Prompt you must have a connection to the database you wish to work on.
We do not support "offline" working where SQL Prompt would continue to provide suggestions even ...
swrobel wrote:
Is there any way to make it stop putting [] around table names? 3.x didn't do that for me...
Please ensure that the option
Sql Prompt 4 > Options > Inserted Code > Special characters > Enclose identifiers within square brackets [] is unchecked.
If it is unchecked, then Sql Prompt should only surround tables with square brackets if there is a sql keyword with the same name therefore making them totally unambiguous.
Can you give an example of a query where this is happening? / comments
swrobel wrote:
Is there any way to make it stop putting [] around table names? 3.x didn't do that for me...
Please ensure that the option
Sql Prompt 4 > Options > Inserted Code > Special chara...
Hi RMD,
Whilst it is true that the database is linked to source control, you would only be committing/retrieving the objects that satisfies your filter.
We don't automatically commit your entire database when you link, so as long as you apply the filter before your first commit, then you should see the behaviour you desire.
Regards
Chris / comments
Hi RMD,
Whilst it is true that the database is linked to source control, you would only be committing/retrieving the objects that satisfies your filter.
We don't automatically commit your entire da...
Hi,
Something that immediately springs to mind (and you'll have to judge whether this would work for you) is to use filters.
You will have to link the database to source control, but before committing your schema objects, filter out the ones you do not want to commit.
This can be done by schema or object name, with/without wildcards. So it depends on how your database is structured as to how easy this is.
The filters are committed to your version control system too, so these can be shared among your database developers using SQL Source Control.
I hope this helps, and let me know if you need help in settings this up.
Regards
Chris / comments
Hi,
Something that immediately springs to mind (and you'll have to judge whether this would work for you) is to use filters.
You will have to link the database to source control, but before committ...
This issue is fixed in the latest release 3.1.4.72.
Sorry for any inconvenience this may have caused. / comments
This issue is fixed in the latest release 3.1.4.72.
Sorry for any inconvenience this may have caused.
Hi sillv0r
It's great to hear that the latest release has solved your issue! [image]
Kind Regards
Chris / comments
Hi sillv0r
It's great to hear that the latest release has solved your issue!
Kind Regards
Chris
HoofHearted wrote:
Brian,
I believe you owe sillv0r an apology. I just downloaded the update made available today and looked in the release notes and found the following:
"Drastically reduced the number of connections made to the SQL Server instance hosting a linked database. This also reduces the number of queries against those databases"
Not only did you dismiss a customer's valid complaint ("barking up the wrong tree", indeed!!), but Red Gate has listed this as a feature instead of a bug fix.
What a slap in the face!! Nice customer service.
Hi there,
I work on the SQL Source Control project, and I would like to apologise for any misunderstanding surrounding the release notes for the recent update.
Listing the connections issue under Features was an error on our part, and is something I have now corrected.
We hope that you find the new release to be a bit faster than the previous few, and look forward to hearing more feedback from you.
Regards
Chris / comments
HoofHearted wrote:
Brian,
I believe you owe sillv0r an apology. I just downloaded the update made available today and looked in the release notes and found the following:
"Drastically reduced th...
Hi,
The latest release (3.1.4.72) which was made available yesterday, has a fix that should stop blue blobs displayed following the first click on a database in a new Management Studio session.
We are aware of some cases where blue blobs are erroneously shown later on in the workflow, but the initial startup one should be fixed.
Could you try upgrading and see if that fixes the problem for you?
Regards
Chris / comments
Hi,
The latest release (3.1.4.72) which was made available yesterday, has a fix that should stop blue blobs displayed following the first click on a database in a new Management Studio session.
We ...