The stereotypes are an “easy” and “toxic” way of grouping and split the people, we can find it in every society and it is extended to the professions. The IT field it is not the exception, in fact, the IT workers profile don’t fit in many of classic “supposed to be” and being realistic, the stereotype is so far to be true, you should read this interesting article in the Wall Street Journal titled “Profile of an IT Worker” (https://www.wsj.com/articles/profile-of-an-it-worker-1382128556).
Author: geohernandez
Deploying SQL Scripts with PowerShell
I always have considered the Continuous Delivery (CD) for Database world as one of the last frontiers to cross, it is not easy at all and the DevOps guys are brave witnesses about it, however, I consider that it is an aim which can be reachable with a mix of effort, compromise and obviously investment (time and money).
The previous aspects mentioned above are from my point of view the most valuable, but we also need to be realistic about in which stage of this process our companies are, I mean, it is not realistic or fair to pretend that a new startup consider spending many resources for implementing DB deployment under
CD vision, but if the team only requires to deploy through a few environments it can be feasible to use a simplistic approach based on using PowerShell.
Dealing with errors for SQL_Variant datatype in MS SQL Server
I have to confess; I have had traumatic experiences with variant data type in my beginning as a software developer, in fact, I always have believed that it is an anti-pattern, at least in the OOP world, on the other hand in the Database world it gains much relevance, Why? Because of every column inside a table is supposed to be a specific datatype, otherwise, it could create a great number of conflicts and uncomfortable situations.
Continue reading “Dealing with errors for SQL_Variant datatype in MS SQL Server”
Generating a Workload for SQL Server
There are some special scenarios where we require to generate a customized workload in our SQL Server instance, these could be specific T-SQL statements as simple queries or stored procedures. In some cases, we need to simulate a workload for troubleshooting common errors related to deadlocks or race conditions, even for testing purposes in which we want to analyze the behavior of SQL Server in
presence of some conditions or data distributions.