Right off the bat – I don’t like plagiarism. I don’t like the idea of it, I don’t like the motives that bring it to light and I don’t like the people who pursue it.
And I don’t like people who waste their time chasing other people in order to blame them that they have plagiarized
Continue reading […] On plagiarism – the concept of borrowing […]
Sorry about the blunt title, but I had no choice.
In a previous post I mentioned how important the design of the database files is. It is important for two reasons: performance and recovery.
Here comes the analogy:
Imagine, you are writing a book. You have written already 500 pages and you are keeping indigo copies somewhere.
Continue reading […] How to risk losing data and how to have most down time […]
Think of a database as a bucket. Actually, scratch that.
Think of the database as a chemistry distillation glassware. Something like this:
Database File Structure
Each database is structured in a way that it has at least one filegroup (containing at least one data file), and at least one log file.
Think of the filegroups as
Continue reading […] The fundamentals of database structure […]