One of the good things, when we have new clients, is that sometimes they have needs that you never heard before. This does not necessarily mean that they are complex. As a matter of fact, they can be really simple..now the question is..are they doable? :-)
From my experience, this can happen mainly because one of two reasons, they have some very specific need, or because the way the application is built will make you work with features that you haven’t played yet.
This post is to answer the question: “You are used to seeing in the format of yyyy-MM-dd right?” that I have raised on my blog post Don’t cutoff yourself with dates in T-SQL – Did you know…
.
As you could see from that blog post, my screen shots were from VSCode and in this case using mssql extension, but this happens also on SQL Server Operations Studio .
This month’s T-SQL Tuesday is brought by Steve Jones ( b | t ) and he wants to know if triggers causes headaches or happiness to us.
This is the 106nd edition of TSQL2sDay - an Adam Machanic ( b | t ) brainchild.
Triggers are those kind of database objects that sometimes are the best bet but most of the times they will strike back.
On 29th September we will have SQL Saturday Porto and I’m proud to announce that I will be speaking!
I will be speaking about dbachecks PowerShell module - dbachecks - Checking SQL Server environments with PowerShell .
The event will be held at ISEP, Rua Dr. António Bernardino de Almeida, 431, 4249-015 Porto, Portugal and you can see the full schedule here .
Register , it’s free!
Almost all the applications we use have a lot of options. And, sometimes we even stumble across them by accident. Who’s ever heard something like “Normal user don’t even use 5% of Excel capabilities!”?
Other options, we know they exist but because the default value it’s ok (so far) we tend to forget it. It is just sitting there, waiting for the day we want/need to change it.
Few days ago I was talking with a friend that show me some “odd behavior” when working with dates on SQL Server.
