Comments
Sort by recent activity
Dan_J said:
Hi all, The latest version of SQL Search contains some minor improvements (related to the feedback received from this forum thread) to database selections within SQL Search. For example, when choosing a selection of databases to search over, SQL Search will now retain those selections, even if you were to click on a database in Object explorer. @GaryH, I also tested the scenario you DM'd me about. That also appears to have been fixed. The latest version of SQL Search can be downloaded here: https://download.red-gate.com/checkforupdates/SQLSearch/SQLSearch_3.6.13.4316.exeI hope this helps!
Thanks! I'll check it out! / comments
Dan_J said:
Hi all,The latest version of SQL Search contains some minor improvements (related to the feedback received from this forum thread) to database selections within SQL Search.For exa...
Actually I think one of the problems is that when I have open tabs and go to close SSMS, I get this error. I have not transactions in progress. TITLE: Querying transaction count ------------------------------ Unable to query transaction count ------------------------------ ADDITIONAL INFORMATION: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054) For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-10054-database-engine-error
------------------------------ An existing connection was forcibly closed by the remote host ------------------------------ BUTTONS: OK ------------------------------ / comments
Actually I think one of the problems is that when I have open tabs and go to close SSMS, I get this error. I have not transactions in progress.TITLE: Querying transaction count--------------------...
JR561 said:
Victoria W said:
Hi @rldawg Please can you try disconnecting SQL server from SSMS Object explore, close then open SQL Search, and then reconnect SQL Server?
This worked for me. It was the explicit:
Disconnect from all open database connections
Closed SQL Search (I closed all other Redgate tabs I had pinned too)
Opened SQL Search
Connected to the database
Yeah it seemed that the open tabs caused some kind of issue because SSMS kept beeping at me when I closed it down with the tabs still open (I leave them open knowing SQL prompt will persist them). Normally that's not an issue. But closing them all explicitly, then closing SSMS and re-opening it worked. / comments
JR561 said:
Victoria W said:
Hi @rldawg Please can you try disconnecting SQL server from SSMS Object explore, close then open SQL Search, and then reconnect SQL Server?
This worked ...
Thanks Tom...but what you are saying to me is that I would need to use qualifed column names 100% of the time when really it is only mandatory when specifying a JOIN condtion. I would need to clutter my column list in a select statement just to get the JOIN condition to be properly formatted.
I personally don't think SQL prompt should ever suggest SQL code that won't syntactically work. / comments
Thanks Tom...but what you are saying to me is that I would need to use qualifed column names 100% of the time when really it is only mandatory when specifying a JOIN condtion. I would need to clutt...
I am using SQL Server 2012. I am searching all object types that contain the word UPC. / comments
I am using SQL Server 2012. I am searching all object types that contain the word UPC.
Ha! Maybe I created it. Sorry, I need to report the bug to myself and fix it!
Although, it's such a good snippet that I thought it was a prepackage one [image]
Another good idea for a snippet called trim:
LTRIM(RTRIM($SELECTEDTEXT$))$CURSOR$
/ comments
Ha! Maybe I created it. Sorry, I need to report the bug to myself and fix it!
Although, it's such a good snippet that I thought it was a prepackage one
Another good idea for a snippet called tr...
Hello Ali,
The private build works perfectly! I went back and modified the proc that I used in the example I provided to you and the suggestion list properly inserted the table variable without square brackets into my T-SQL code.
Thank you and the team for the efforts!
Robert / comments
Hello Ali,
The private build works perfectly! I went back and modified the proc that I used in the example I provided to you and the suggestion list properly inserted the table variable without squ...
It's deprecated in future versions of SQL server. I am using SQL 2012 and others still use SQL 2008.
My contention is that SQL prompt should always provide suggestions that are syntactically correct and will actually work.
You will note that you're jumping the gun on a deprecated feature. It hasn't even been determined when 3 and 4 part naming will not be supported.
The following SQL Server Database Engine features are supported in the next version of SQL Server, but will be removed in a later version. The specific version of SQL Server has not been determined. / comments
It's deprecated in future versions of SQL server. I am using SQL 2012 and others still use SQL 2008.
My contention is that SQL prompt should always provide suggestions that are syntactically corr...
Thanks for the update.
Without aliasing the tables, it's impossible to avoid. I find it hard to believe that MS and Red-Gate are telling me that I must alias tables in order for joins to work properly in the future. And perhaps that's why they haven't gotten rid of 3-4 part naming capability yet. Aliasing has always been optional, not required.
Thank you for addressing my concerns, I appreciate the feedback and the consideration.
Thanks,
Robert / comments
Thanks for the update.
Without aliasing the tables, it's impossible to avoid. I find it hard to believe that MS and Red-Gate are telling me that I must alias tables in order for joins to work prop...