Comments
Sort by recent activity
cstrub said:
Found an easy solution, locate SQLPrompt.Format.CommandLine.exe on your computer (was in "D:\Program Files (x86)\Red Gate\SQL Prompt 9" on my computer). using Visual Studio (File-->Open on the EXE) correct the Product Version from 10.14.22.11347+e4f26ea... to 10.14.22.11347). The issue is the Product Version for the file isn't valid for using with System.Version(string) method. Hope this helps someone else who likes to be able to use SQL Prompt and SQL Compare
Thank you, did the trick for me also. / comments
cstrub said:
Found an easy solution, locate SQLPrompt.Format.CommandLine.exe on your computer (was in "D:\Program Files (x86)\Red Gate\SQL Prompt 9" on my computer).using Visual Studio (File-...
Not an issue as much. Just noticed when I ran it for the first time, it wanted to log in to your licensing server.
On this particular server, it was not a problem as it can connect, however thinking bigger picture and perhaps long term, we have some SQL servers in our SCADA environment which do not connect. Wondering how/if it would work there.
Cheers,
H / comments
Not an issue as much. Just noticed when I ran it for the first time, it wanted to log in to your licensing server.
On this particular server, it was not a problem as it can connect, however thinki...
Ok, thanks.
H / comments
Ok, thanks.
H
This also applies if output is set to PDF.
I tried the hack mentioned above and still fails, when it's at Finalising documentation 99% and memory usage gets to just over 3GB. I'm guessing it's trying to create the actual file on disk at this point.
Running on SQL Server 2008 R2.
Can't believe a 64bit version isn't available yet.
Cheers,
H / comments
This also applies if output is set to PDF.
I tried the hack mentioned above and still fails, when it's at Finalising documentation 99% and memory usage gets to just over 3GB. I'm guessing it's try...