February 6, 2017 at 10:19 pm
Comments posted to this topic are about the item The differential PoSh backup
February 6, 2017 at 10:21 pm
Really need to get back into PowerShell.
That last project has rusted my mind (all things modern were taboo)
Thanks for the question, Steve.
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
February 7, 2017 at 6:19 am
This is exactly why I can't get behind PowerShell (and many other Microsoft things, for that matter.) It's an excellent tool which I use to automate many things, but it's hard to recommend something littered with obvious blunders like this.
There's a significant difference between an incremental and a differential backup, and although it may be considered specialist knowledge, at the very least I'd expect the team working on the SQL backup applet to know which one actually exists in SQL Server.
The level of organizational dysfunction which would allow this broken parameter through all levels of testing and QA through to a public release boggles my mind.
February 7, 2017 at 7:13 am
Confession - used msdn
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
February 7, 2017 at 7:16 am
lol @ the docs:
Indicates that a differential backup is performed.
Yeah gotta agree with sknox, how hard would it have been to match up the keywords? Theres a principle involved, "least astonishment", if you read Wikipedia they have listed what could be a good summary:
A textbook formulation is: "People are part of the system. The design should match the user's experience, expectations, and mental models."
February 7, 2017 at 9:34 am
sknox - Tuesday, February 7, 2017 6:19 AMThis is exactly why I can't get behind PowerShell (and many other Microsoft things, for that matter.) It's an excellent tool which I use to automate many things, but it's hard to recommend something littered with obvious blunders like this.There's a significant difference between an incremental and a differential backup, and although it may be considered specialist knowledge, at the very least I'd expect the team working on the SQL backup applet to know which one actually exists in SQL Server.
The level of organizational dysfunction which would allow this broken parameter through all levels of testing and QA through to a public release boggles my mind.
patrickmcginnis59 10839 - Tuesday, February 7, 2017 7:16 AMlol @ the docs:-Incremental
Indicates that a differential backup is performed.
Yeah gotta agree with sknox, how hard would it have been to match up the keywords? Theres a principle involved, "least astonishment", if you read Wikipedia they have listed what could be a good summary:
A textbook formulation is: "People are part of the system. The design should match the user's experience, expectations, and mental models."
+1
Confession - the correct answer I found in the documentation easily, but quite unnecessarily, I dealt with the problem of Incremental vs. differential backup... :angry: I found an article "Does SQL Server have incremental data backups?" and I've been going through this forums: "What is the difference between incremental backup and transaction log" and finally "How to Take Incremental Backup in sql server".
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply