How can we help you today? How can we help you today?
tbostrup
Great - Where do I get the latest Beta/preview of SQL Data Compare 8? (It doesn't appear to be released yet). My previous 8.0 beta download has "trial expired". We use 7.1 for production work ATM. / comments
Great - Where do I get the latest Beta/preview of SQL Data Compare 8? (It doesn't appear to be released yet). My previous 8.0 beta download has "trial expired". We use 7.1 for production work ATM.
0 votes
It happened once - I have not tried to reproduce it. VS 2005 Team Suite with DBPro Solution: 2 DB projects 2 DB test projects (VB.Net) 1 class library project (C#) with DBPro custom test One module in the DB test project has a large .resx file (33,149 lines), including a single test event script of 27,008 lines. Sequence that led to the NullreferenceException (from memory): 1: Started a Replace All in Entire Solution to replace "somedbname" with "$(somedbname)" in 3-part names (when documenting this several days later, I think it may be possible that I replaced "somedbname." with "$(somedbname)", but I don't really think I did). 2: Replace All would "hang" in one file for several minutes (it may have been the large .resx file, or maybe a stored proc containing 37085 lines, most of which contain database reference, I'm not sure). 3: I cancelled the "hanging" replacement - and that seemed to "hang" also. 4: I repeated the replace, which would now complete and indicate 175 replacements. 5: I then closed VS 2005 (clicked X), and got the error message. Afterwards, I realized that the setvar variables (which are based on SQLCMD variables) probably won't work in the database test event scripts (since those are not SQLCMD enabled AFAIK). HTH and Thanks, Tore. / comments
It happened once - I have not tried to reproduce it. VS 2005 Team Suite with DBPro Solution: 2 DB projects 2 DB test projects (VB.Net) 1 class library project (C#) with DBPro custom test One module...
0 votes
I would get this message with a couple of dat files in this folder and lockfile.pid in the parent folder being compressed. Permission were ok, no read-only attributes. I'll see how it goes... SQL Backup version 5.4.0.55 / comments
I would get this message with a couple of dat files in this folder and lockfile.pid in the parent folder being compressed. Permission were ok, no read-only attributes. I'll see how it goes... SQL...
0 votes