Activity overview
Latest activity by Not_Happy
It is answer like this that left me in despair when I originally raised it. Server configurations may not be in the gift of a lot of developers working in corporate environments. But that aside, looking for something to say "ah ha, it's x that you're doing" doesn't help either. The admission that Source Control (another product I am forced to use) will struggle with a large number of objects in a database, is a staggering admission. You're website makes lots of claims about "large" databases but it seems that what you consider large is not all that large in the real world. This all still comes down to poor memory management and error trapping. Whatever causes your app to run out of available memory should be a scenario you're handling. Judging by the admission above, and my experience with SQL Prompt, it's not. For the above, surely the simplest thing is to check for a change on an object, and either write that change or move on. In both cases, you can make the memory available again so you're only using a small amount. This is a simple scenario, I know, but the principle holds true. / comments
It is answer like this that left me in despair when I originally raised it. Server configurations may not be in the gift of a lot of developers working in corporate environments. But that aside, lo...
The theory is that it will handle things, but based on experience with Redgate software, it often doesn't handle things at all well. we've had multiple occasions when we've had to have them supply us with urgent patches to fix things. We've only just started using SQL test and already I've discovered a number of things that don't work properly. Since we have a very large scale system I want to ensure that I am in complete control of what happens in the database / comments
The theory is that it will handle things, but based on experience with Redgate software, it often doesn't handle things at all well. we've had multiple occasions when we've had to have them supply ...
I'm not sure that will work. Doesn't the assert proc reference the temp tables used for the results by passing the names to Private_CompareTables? This wouldn't work with table variables. / comments
I'm not sure that will work. Doesn't the assert proc reference the temp tables used for the results by passing the names to Private_CompareTables? This wouldn't work with table variables.
Transactions
I have just created a unit test that, because of the way our environment has been configured, drops a series of objects prior to generating the data/objects under test. In order to maintain the int...
Another unreliable product
I've just run this through to compare two versions of a database. The first time I used the default settings and found it picked up hundreds of items where the difference was constraint names.I've ...
Unfortunately, Alex, it does not. Splitting hairs over the analogy isn't helpful. The bottom line is you have a product that you sell, for a not insignificant amount of money, that isn't capable of fulfilling the task it purports to do. Relying on the limitations imposed by SSMS as a justification for the failures of your product is a lazy excuse for poor coding. With better coding you could make smarter use of available memory and manage your product's use of that memory better. Would you eat a stale sandwich if the retailer said it's all we've got? Of course not, but you still expect your customers to pay for software that you know doesn't do the job properly. / comments
Unfortunately, Alex, it does not.Splitting hairs over the analogy isn't helpful.The bottom line is you have a product that you sell, for a not insignificant amount of money, that isn't capable of f...
No response? It doesn't fill me with confidence. I'm forced to use some of your products because that's my client's choice of tool, however, SQL Prompt is something designed to make my work easier, yet having it crash, repeatedly, more than once a day, does the exact opposite. The benefits of being able to type AP and get the proc are far outweighed by the crashes and incomplete results. SSMS doesn't crash when I try to execute a big script, so why does your tool? I've reached the point where I am uninstalling it since it's making my job harder not easier. / comments
No response? It doesn't fill me with confidence.I'm forced to use some of your products because that's my client's choice of tool, however, SQL Prompt is something designed to make my work easier, ...
Thank you for replying. I've read that post and it seems to say "if our tool doesn't work, change other things so it can". Sorry to be blunt, but that's a nonsense answer. If a tool doesn't have the facilities to run, it should exit gracefully, not bring the entire system down or prevent perfectly valid code from executing. If my electricity supply goes down whilst I'm using the bandsaw, it doesn't make the entire house collapse. It's your code, if you don't have the resource available, stop your code. Your tools are add-ins supposedly to make my development quicker and easier. It's farcical to suggest that users change their practices because your tool wants to work within specific constraints. Whether those constraints are imposed on you by the OS or SSMS is irrelevant. We all tend to use these tools in professional environments and so more disks, smaller tables, shorter procs are often out of our control. There is never a question where the answer is change the question. / comments
Thank you for replying. I've read that post and it seems to say "if our tool doesn't work, change other things so it can".Sorry to be blunt, but that's a nonsense answer. If a tool doesn't have the...
Out of Memory Exception
This seems to a common thread with Red-Gate tools. There are lots of reports of this error when using pretty much any of the Red-Gate tools.When is this going to be addressed? It is fairly predicta...