Upon execution of a script a server must be selected in most cases. The pulldown list should be populated with previously entered servernames3 votes
To be able to run the script in SQLCMD Mode = ON2 votes
It Would be very useful if you could point to a TSql script and it will create the relevant xml file etc... for you. I think it will simplify things quite a bit2 votes
Shouldn't the table control be able to be referenced in a SQL script?
<control type="header" label="Select server and database:"><font name="Arial" size="12" /></control>
<control type="table" id="tblname" /></block></ui>
Failure while running DB Get Columns for table : Failed to execute SQL
Must declare the scalar variable "@tblname".2 votes
The control for table includes tables only and does not include user defined views. There is no control that gives a dropdown of views. You could make the table control configurable: tables only/views only/both tables and views. And/or create a separate view control.2 votes
Tried to run a script on a SQL 2000 box but got the error message: SQL Scripts Manager supports only SQL Server 2005 and later. While the documentations says SQL Scripts Manager is compatible with:
* SQL Server 2000, 2005, 2008, 2008 R2
* Windows 2000, Windows XP, Windows Vista, Windows 7, Windows Server 2003, Windows Server 2008
I actually wrote my script to overcome a bug that is only in SQL 2000 - works fine in 2005 and above.2 votes
This should be added under the preset combobox / open button, and will greatly enhance the speedyness of this fine app :)2 votes
Remember results screen size and window state. If it was maximized or sized a certain way, show it in the same location next time a query is executed.2 votes
Having 28 scripts is far from enough for a script manager, please include much more scripts for performance, security and DBA functions.1 vote
Copy and pasting this code causes and error in SSM. "mode" is not valid.
<control type="list" id="options">
If use the following convention in lots of scripts/stored procedures:
--determine Office Id
Select @office_id = Office_Id from Lookup_Office where Office_Description = @office_description
set @count = @@rowcount
If @count <> 1
Raiserror('An error was generated looking for the Office.', 18,1)
All script manager does is report 'Failed'. Can it please return the raiserror message so I can see where in the script it did fail?
Dave J1 vote
When I run a script I don't get any result shown anywhere.
Initiate a voting drive on the connect item to make the ssms template explorer refreshable. Using the export scripts from phil factor this is an issue. http://connect.microsoft.com/SQLServer/feedback/details/338542/ssmss-sql-server-template-doesnt-refresh-automatically1 vote
It seems like these would be easier to work with and quicker to use if they were just snippets in SSMS via SQL Prompt...
I don't really see the point of a separate app.1 vote
Add tooltips that show more of the cell content when the text in the cell is long. For example, running "CPU-intensive queies" you can't see much of long sql statements in the tooltip. You have to double click to see cell content.1 vote
Make the Cell Content screen format CR/LF correctly instead of auto wrapping everything. Possibly give a checkbox to do so (and remember the setting). For example, running "CPU-intensive queies" returns cells that show the SQL statement. The statement would be more readable if the existing line breaks in the statement were preserved. Also allow showing sql syntax coloring like you see when you click "Script Details" or the "View Script" button. Maybe a checkbox to enable/disable that since it won't always be SQL in the cell content. Or allow the script author to denote in the XML file which result columns are SQL and which are not so the tool can determine whether it should be syntax colored.
Make the Cell Content screen format CR/LF correctly instead of auto wrapping everything. Possibly give a checkbox to do so (and remember the setting). For example, running "CPU-intensive queies" returns cells that show the SQL statement. The statement would be more readable if the existing line breaks in the statement were preserved. Also allow showing sql syntax coloring like you see when you click "Script Details" or the "View Script" button. Maybe a checkbox to enable/disable that since it won't always be SQL in the cell content. Or allow the script author to denote in the XML file which result…1 vote
BUG: Latest version (126.96.36.199) gives error when calling $progress.RowValue from powershell script. Gives following error:
Method invocation failed because [#iJ0.#JXA] doesn't contain a method named 'RowValue'.1 vote
it's totally incomprihensible GUI1 vote
- Don't see your idea?