In the last post of the year I’ll talk about knowledge and how we are continuously learning. The idea of the topic comes from a Packt Publishing offer: selling books for Xmas for $5.
It doesn’t matter our job, it’s changing, so we’ve to evolve too. In fact, I don’t know any job that you don’t have to improve your skills continuously usually . . .
In PostgreSQL, when you’re working with sequences, if you insert a future value due to the incrementing values, you will get an error when that value is going to be inserted. I like much more how SQL Server handles autoincrement columns with its IDENTITY property, that would be like the sequences linked to a table like SERIAL, but it’s much . . .
Disclaimer: I was asked to review the Getting Started with OrientDB book and I received a free ebook copy of it.
OrientDB is defined in its website as: an Open Source GraphDB with a mix of features taken from Document Databases and Object Orientation. It’s a new and promising database. But it’s has little documentation and it’s quite . . .
There’s a project in my company that has a dedicated PostgreSQL virtual server with 12 cores and 32 GB RAM and it’s exclusively being used by one developer. He told me that he had an error with a query and checking the log file I could find: “ERROR: could not write block XXXX of temporary file: No space left”. But there were 27 . . .
I needed a hash function that I could pass a text string or a file to compute its hash (MD5, SHA1, etc…). But unfortunately Powershell hasn’t got one, so I started to look for alternatives:
- There’s a Get-Hash cmdlet (function embedded in a DLL written in C#) in PowerShell Community Extensions (PSCX) module.
I found two small tools . . .
When there’s a table with a primary key that is an IDENTITY and you want to remove the IDENTITY property, there’s no simple SQL code to do it. It is not a trivial task. In fact, there’re many steps to be done and it’s better to do all of them inside a single transaction, to avoid to leave the database in a inconsistent way (without FK, or . . .
I’ve found three ways of getting user permissions (grants and denies) in SQL Server:
- SQL Server Management Studio: It’s OK and user-friendly. But it’s not an option if you’ve a large farm of servers or you want to script it and create task to run the checks.
- Impersonate as the user and check its permissions.
- SELECT on system tables to see . . .