Comments
Sort by recent activity
No response from anyone? Someone at Redgate?
RG sql data compare is clearly showing a quick "Cancelling .... something ... " and starting over. Infinite loop. making my expensive software not very useful in this case. I've run into this with a few other comparisons (user databases) since I noticed this issue on Monday. / comments
No response from anyone? Someone at Redgate?
RG sql data compare is clearly showing a quick "Cancelling .... something ... " and starting over. Infinite loop. making my expensive software not ve...
Don't let the simplicity of the example fool you.
Amanda is now managing 100 databases, each with thousands of objects and is put in the same situation...
Your suggestion of retrieving the missing objects (CHANGING the current truth), then dropping it (using what as a guide, a screen shot or a had written list?), simply to allow SSC to get its bearings is untenable in a situation where there are potentially hundreds of objects to process.
WHEN a DB is linked to a TFS node (or to what node) should have no bearing on the ability of the tool to capture the current shape of the DB in your source control system.
I'm really curious what the answer to this is. If you have an older version in a DB linked to TFS and a newer version in another DB, the best workflow I can think of (which isn't very appealing) is using SQL compare to sync the new db to the old and then use SSC to check in.
I don't understand why the physical action of a drop against a currently linked db is required to check in the absence of an object. / comments
Don't let the simplicity of the example fool you.
Amanda is now managing 100 databases, each with thousands of objects and is put in the same situation...
Your suggestion of retrieving the missing ...
haleyjason,
I truly appreciate the input. I would also (really) appreciate a little background on what's going on.
I was under the impression that if an assembly is in the GAC it is available to all .NET processes on the system, this being the purpose of the GAC. I never really paid much attention to the "Process architecture" attribute displayed there. So I'm admitting my naivete in this area and asking for some explanation of what's happening under the covers.
If an assembly is in the GAC but showing as MSIL, does that affect the assembly's visibility system wide?
I explained what my ultimate goal is, this crystal assembly is in the GAC_MSIL and a web application is failing to fulfill it's reference to that dependency.
How should I proceed? / comments
haleyjason,
I truly appreciate the input. I would also (really) appreciate a little background on what's going on.
I was under the impression that if an assembly is in the GAC it is available to a...
I've done this, but reflector doesn't see the assembly I'm looking for.
My asp.net web app is dying looking for CrystalDecisions.CrystalReports.Engine version 10.5.3700
I can see it in the GAC, but reflector doesn't? It is MSIL.
can someone explain what's going on? / comments
I've done this, but reflector doesn't see the assembly I'm looking for.
My asp.net web app is dying looking for CrystalDecisions.CrystalReports.Engine version 10.5.3700
I can see it in the GAC, but...
Yes, same result.
Someone else here also went to the same link and got the same results. However, he then took off the file name to browse the location and was then able to see the file and download it normally.
we've got the file, but you may want to test your link from other locations. I've never seen this behavior before for a ZIP file. / comments
Yes, same result.
Someone else here also went to the same link and got the same results. However, he then took off the file name to browse the location and was then able to see the file and downlo...
Originally I was comparing the DB to a previously cloned version. However, even comparing the DB to itself gives the error. / comments
Originally I was comparing the DB to a previously cloned version. However, even comparing the DB to itself gives the error.
Dan,
Of course you need a time limit, but setting it the same as that of a full release version is pretty restrictive, especially when it expires even before the release date! This is the first instance I've ever seen that situation.
Your first Beta had no time limit, right? At least I didn't notice, because I ran it, liked the concept, spent a few days playing and commenting on the forum, and then got board and forgot about it till Beta 2.
If you're concerned about the Beta 2 harming sales, make it a time limit that extends beyond the projected release date by 30 or 45 days...
It's not going to kill your sales, as those that are using it often are GOING TO BUY THE REALEASE!! Those that don't weren't going to buy it anyway so an extra month of use is irrelevant to red-gate.
But then again, why would someone bother beta testing a product they have no interest in using? And, why would you ever want to treat beta testers just like some user trying a demo? They are spending their time HELPING you with a product that, by definition, isn't ready for prime time. If you think you can release a working product that fully solves the majority of users' needs and has no bugs, based solely on developers' opinions, I've got some land to sell you in Florida!
Has red-gate learned nothing from MS's new approach using CTPs and "interactive" product development? / comments
Dan,
Of course you need a time limit, but setting it the same as that of a full release version is pretty restrictive, especially when it expires even before the release date! This is the first in...
I had just changed the Application Options to use a different SQL editor. I used double quotes for the path, since it was in progra~1...
removing the dbl quotes prevents the exception. / comments
I had just changed the Application Options to use a different SQL editor. I used double quotes for the path, since it was in progra~1...
removing the dbl quotes prevents the exception.
Diddo, diddo, diddo.
another button to "copy all" is just too obvious. / comments
Diddo, diddo, diddo.
another button to "copy all" is just too obvious.