Activity overview
Latest activity by Roust_m
Renaming a script feature request
Hi,
It would be nice to have an ability to rename a script listed for execution instead of having to use "save as" and later deleting the old script. I guess it is easy to implement via right mous...
Yep, similar to what I am doing now, but this does not cover the whole thing, as there may be a job step parameter which is country specific.
E.g. for UK it would be:
exec spMySP 'Products','UK'
for France:
exec spMySP 'Produits','FR'
for China:
exec spMySP '產品','CN'
and the generic script would look like:
exec spMySP '{Product translation}','{Country code}'
therefore it should also handle unicode.
I understand that I can build a replacement table in the begining of the script. E.g.: if the last two characters of the database name equal to 'FR' then replace {Product translation} with 'Produits' and '{Country code}' with 'FR', but it would be easier to build separate scripts.
It would be ideal if the app could search for the tags and prompt me to set the replacements for each database I am running the script against. / comments
Yep, similar to what I am doing now, but this does not cover the whole thing, as there may be a job step parameter which is country specific.
E.g. for UK it would be:
exec spMySP 'Products','UK'
fo...
But what if you have something like this:
USE MyDB
[do some schema changes here]
USE msdb
[create some jobs here]
if you ignore all USE statements your script may fail.
I would rather have an ability to do automatic replacements like this:
USE {database name}
[do some schema changes here]
USE msdb
[create some jobs here]
So {database name} would automaticaly be replaces to the database the script runs against. / comments
But what if you have something like this:
USE MyDB
[do some schema changes here]
USE msdb
[create some jobs here]
if you ignore all USE statements your script may fail.
I would rather have an abili...
Database specific tags
Hi,
I think it would be very useful to have a feature to automatically replace some text inside the TSQL script depending on the database it will run against. Suppose I have three databases called...