Comments
Sort by recent activity
That does sound handy.
Thanks!
-Jeff / comments
That does sound handy.
Thanks!
-Jeff
David,
I don't know why I didn't think of using Tortoise to update the local directories to the "older" version. That makes a lot of sense. We can do that.
Although, our Data Architect would like a button (or a context menu item) in SSC to tell it to rebuild the working base from the database :lol:
Thanks,
-Jeff / comments
David,
I don't know why I didn't think of using Tortoise to update the local directories to the "older" version. That makes a lot of sense. We can do that.
Although, our Data Architect would like...
Over the course of 3 months we had made over 100 new objects and about 400 other object changes across 4 databases as part of a warehousing project. Unfortunately, for various business reasons, we couldn't deploy all of those changes at once. So, we deployed all of the new objects to the production environment and then we wanted to do more testing with a portion of the object changes. Before doing this we wanted our testing environment to look just like the production environment. We were relying on SSC to help us identify all of the objects that required changing. When none of them showed up our Data Architect freaked. He crawled back from the ledge after we relinked the databases on his machine and the differences showed up again.
With the volume of changes he was making, I'm not sure this workaround would be a lot better than unlinking and relinking his machine. But, it definitely seems better for just a handful of changes.
-Jeff / comments
Over the course of 3 months we had made over 100 new objects and about 400 other object changes across 4 databases as part of a warehousing project. Unfortunately, for various business reasons, we...
This thread was timed perfectly as I just ran into the same issue and the suggestion helped me out. However, I have a comment related to the UI and the default value for MAXDATABLOCK.
The UI shows a maximum value of 2048 KB and it's the MAXTRANSFERSIZE that has a max of 1024 KB. Looking at the defaults on the screen, I thought the parameter may have been mislabeled in the thread so I changed the MAXTRANSFERSIZE to 512 KB then to 128 KB (I figured I'd work my way down until it worked to get the most speed available) and got the same errors. I changed the MAXDATABLOCK to 1024 KB and my backups started running again. So, I think the parameter name is correct, but perhaps the values are mis-stated? Or am I understanding this incorrectly? I'm also running version 6.5.1.9. / comments
This thread was timed perfectly as I just ran into the same issue and the suggestion helped me out. However, I have a comment related to the UI and the default value for MAXDATABLOCK.
The UI shows...