First thank you for this app; looks great. Just wanted to get some feedback about others performance experience. I'm running this on an older laptop 1+ GB RAM, scripting 886 objects. That took about 5 minutes. Does that sound about right?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, that sounds close. SQL-SMO issues a gazillion queries, so network latency can be an issue. But something in the neighborhood of an-object-per-second is what I am experiencing.
Richard
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That was my experience. Running locally was relatively quick. When I ran against our DataCenter (VPN connection to a remote location), the time was incredibly high - took almost 2 hours for the database I was scripting. Ouch! Of course, I haven't had a chance to try the new version yet and plan to do that soon. My big concerns now are around how to branch and compare these files (typical source-control related questions).
-Pete
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
FYI - running against that remote server, it seems to be taking about 5 seconds per object. I started something up a while ago against a DB where everything should be pretty well cached and it's still running. It works, but it's really slow. I know that if I run locally, it's quite a bit faster. No idea if there's a way to open an SMO connection and leave it open rather than re-connecting all of the time, but if there is, that may be an option to speed things up some.
-Pete
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Another update - the task finished against my remote server. It took 2:35 minutes to script out 1,595 objects from my remote database. Just wanted to give you an update on that. I know latency falls into this somewhere, but this seems a little more than expected.
I like the direction the project is heading and the functionality is great so far. The latency issues are painful, though.
-Pete
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First thank you for this app; looks great. Just wanted to get some feedback about others performance experience. I'm running this on an older laptop 1+ GB RAM, scripting 886 objects. That took about 5 minutes. Does that sound about right?
Thanks.
Update on last post. That took 10 minutes. (Didn't notice the time stamp at the end. Another good feature!)
Yes, that sounds close. SQL-SMO issues a gazillion queries, so network latency can be an issue. But something in the neighborhood of an-object-per-second is what I am experiencing.
Richard
That was my experience. Running locally was relatively quick. When I ran against our DataCenter (VPN connection to a remote location), the time was incredibly high - took almost 2 hours for the database I was scripting. Ouch! Of course, I haven't had a chance to try the new version yet and plan to do that soon. My big concerns now are around how to branch and compare these files (typical source-control related questions).
-Pete
FYI - running against that remote server, it seems to be taking about 5 seconds per object. I started something up a while ago against a DB where everything should be pretty well cached and it's still running. It works, but it's really slow. I know that if I run locally, it's quite a bit faster. No idea if there's a way to open an SMO connection and leave it open rather than re-connecting all of the time, but if there is, that may be an option to speed things up some.
-Pete
Another update - the task finished against my remote server. It took 2:35 minutes to script out 1,595 objects from my remote database. Just wanted to give you an update on that. I know latency falls into this somewhere, but this seems a little more than expected.
I like the direction the project is heading and the functionality is great so far. The latency issues are painful, though.
-Pete