Comments
Sort by recent activity
Robin
Unfortunately, we'll have to wait until v6 is released before I can try level 4 compression on the production server.
However, I ran a few small trials with differeing thread counts on v5.4.
The default of 15 threads took 00:04:10
Cutting this to 7 threads 00:04:13
Raising it to 22 threads 00:04:16
It's difficult with such a small total duration to see whether these are actual changes or just caused by prevailing resource conditions on the server during the working day.
I guess we'll have to wait a while for the DB sizes to start increasing or for more customers to transfer operations into the hosted environment before we can see a substantial increase in duration.
Feels really surreal to be wishing for backups to take longer ;-)
Regards
Andy / comments
Robin
Unfortunately, we'll have to wait until v6 is released before I can try level 4 compression on the production server.
However, I ran a few small trials with differeing thread counts on v5.4.
...
That was pretty much our Customer's response too :-)
It's a hosted DW solution.
Being DW, the data is pretty compressable, but the hosting company's server is really impressive. If I remember correctly, the native backup for this DB to the same disk only used to take just over 3 minutes / comments
That was pretty much our Customer's response too :-)
It's a hosted DW solution.
Being DW, the data is pretty compressable, but the hosting company's server is really impressive. If I remember corr...
It's fantastic to see that someone has been able to test this feature and that it works as advertised - there are too many users of our test system for me to be able to unplug it.
I'm going to find this feature invaluable in the operational environment as our txlogs backup directly to an offsite location.
Personally, I'd still like to see a warning that the job completed with network glitches. Mostly because it would alow me to spot potential network or NIC degradations before they become too much of an issue.
Andy / comments
It's fantastic to see that someone has been able to test this feature and that it works as advertised - there are too many users of our test system for me to be able to unplug it.
I'm going to find...
Good point.
I'd overlooked the fact that this server is on a separate subnet and is not a member of the main company domain. This is the reason for using a local login to connect
It's part of a workgroup containing around 5 servers with the default name of 'WORKGROUP'. / comments
Good point.
I'd overlooked the fact that this server is on a separate subnet and is not a member of the main company domain. This is the reason for using a local login to connect
It's part of a wo...
Nigel
The local login was 'devuser'
The servername was PV_LPDATA_01
2 underscore characters in the name - nothing illegal or even uncommon in that.
I'm logged in via remote desktop using this user, and a query session returns exactly those details when I retreived the value of SUSER_SNAME()
Thanks
Andy / comments
Nigel
The local login was 'devuser'
The servername was PV_LPDATA_01
2 underscore characters in the name - nothing illegal or even uncommon in that.
I'm logged in via remote desktop using this user,...