Comments
4 comments
-
Hi,
thank's a lot for posting. These are all very sensible suggestions which we will try and incorporate into the next version.
Regards,
Tilman -
PS: We do save the options in a file. You can find the file here
%userprofile%\Local Settings\Application Data\Red Gate\SQL Prompt\Options.xml. -
As far as the config file goes, this is great. Only problem is, as I said, I like to run the software off of my usb drive that way I can use it on any computer. Since you are storing the config in a user directory this still wouldn't help me with always having my config with me. I would either need to have the config file stored in the same location as the exe (or a sub directory of it), or maybe you guys could add a command line switch to tell the program where to look for the config file. That way I could point the program to the config file located on my usb drive.
Thanks. -
Hi,
I have added your suggestion to our list. For the moment you could manually move the config file around, although, I admit that that is less than ideal.
Regards,
Tilman
Add comment
Please sign in to leave a comment.
Another thing I would like to see is the storing of the settings in an ini or config file or something. I have SQL Prompt installed on a 120Gb Portable USB drive so that I can use it from different places. I currently develop on a minimum of 3 systems (Desktop, Laptop, Workstation). And so it would be nice to have the settings be file based, as then I would have the same settings and "Connections" from anywhere that I open the program. This would be much more useful for me.
One more feature I would like is for the program to be able to save a "Server Connection" instead of just a "Database Connection". It would be nice to be able to save connection settings for a server instead of for a database. Say i have server123 with 25 databases, but all my database logins are the same on that server. Right now SQL Prompt needs to save all 25 database connections. And each time I need to use SQL Prompt with a different database on that same server, I basically have to create a duplicate connection to the server with the only difference being the database name. But the username and the password are the same. So, for me, it would be nice to create a connection to the server with username "ABC" and password "123", and then have SQL Prompt try this login information for every database on that server that I try to connect to. And then if that login fails, it can prompt me to save a direct connection to the individual database that I am trying to connect to. Make sense?
Well, those are a few little things that I would like to see in SQL Prompt. I hope my descriptions made sense are and adequate.