Activity overview
Latest activity by delux
RedGate License - per user or per machine?
If I log into the same machine with multiple accounts (testing), do RedGate products appear registered for each user profile on the same machine, once they have been registered once? Or do they re...
Wow, I guess I've just never tried to name something that. I just tried to create a file prn.txt and it did not work. Good catch!
Thanks! / comments
Wow, I guess I've just never tried to name something that. I just tried to create a file prn.txt and it did not work. Good catch!
Thanks!
Snippet Manager
If I try to add a snippet titled "prn" (without quotes), I get an error message below. However, if I change the name it works fine.
SQL Prompt cannot save this snippet to the folder:
C:\ Users\<pr...
Second instance of SSMS add in fails
I have run SQL Prompt and Refactor for several years. Recently we upgraded to Windows 7 and when I open SSMS, it works fine, but a second instance, everything is grayed out. Well, more specifical...
David, did this make sense? This would be really helpful if it's possible using SQL Prompt or Refactor. We have hundreds of existing stored procs that will not compile in our new case-sensitive SQL server without touching each one of them and making all the variables/stored proc/table name references match in case to the objects and declerations. / comments
David, did this make sense? This would be really helpful if it's possible using SQL Prompt or Refactor. We have hundreds of existing stored procs that will not compile in our new case-sensitive S...
No, camel-casing was just example. It's just basically making case-sensitive any custom code. The variable/stored proc/table name/etc. could have been previously been declare like this @..., and in a case-insenstive environment used later on like this @..., but I need all references to a variable/stored proc/table name/etc. to match their decleration or definition case. / comments
No, camel-casing was just example. It's just basically making case-sensitive any custom code. The variable/stored proc/table name/etc. could have been previously been declare like this @..., and ...
Correction:
--original
SELECT @var = aCol FROM linkedServer.dbo.aTablename --case corrected from linkedServer.dbo.aTablename to linkedServer.dbo.aTablename
--auto-format
SELECT @Var = aCol FROM LinkedServer.dbo.aTableName --case corrected from linkedServer.dbo.aTablename to LinkedServer.dbo.aTableName / comments
Correction:
--original
SELECT @var = aCol FROM linkedServer.dbo.aTablename --case corrected from linkedServer.dbo.aTablename to linkedServer.dbo.aTablename
--auto-format
SELECT @Var = aCol FROM Lin...
Yes, my apologies for not doing that originally. This is a really simple example, but basically we have 100s of stored procs that were built in a case-insensitive SQL environment that need to be corrected to work in a case-sensitive environment. It would be great if there was some script that could be run to fix it, but it's not a problem to open each one up and click an auto-format button and ALTER the stored proc. Thanks for your time.
--original
DECLARE @Var AS INT
SET @var = 1234
SELECT @var = aCol FROM linkedServer.dbo.aTablename --actually looks like this in database LinkedServer.dbo.aTableName
EXEC dbo.aStoredProc --actually looks like this in database dbo.aStoredPROC
--auto-format
DECLARE @Var AS INT
SET @Var = 1234 --case corrected from @var to @Var
SELECT @var = aCol FROM linkedServer.dbo.aTablename --case corrected from linkedServer.dbo.aTablename to linkedServer.dbo.aTablename
EXEC dbo.aStoredPROC --case corrected from dbo.aStoredProc to dbo.aStoredPROC / comments
Yes, my apologies for not doing that originally. This is a really simple example, but basically we have 100s of stored procs that were built in a case-insensitive SQL environment that need to be c...
format formally case-insensitive code
We're moving from a case-insensitive to a case-sensitive SQL 2008 platform. We are not in control of the new platform and need a quick way to do a one-time update to not only keywords (which I kno...
Feature Suggestion: Allow Change and Execute code
Selection that has been returned as a search result. Allow user to change the code and alter the stored proc to save the changes. This would save time instead of having to double-click the search...