SQL Server provides two different forms of authenticating the users that connect to the database server: Windows Authentication, which is the default and preferred method, and SQL Server Authentication, which needs to be explicitly enabled.
Today I want to tell you about an issue we ran into while working on one of our customers and, while it’s easy to understand when explained, it might be tricky to get done when you don’t look at the whole picture.
According to a survey by Verizon, the financial services industry experiences 35% of total data breaches. This is the highest percentage of any sector. It’s therefore unsurprising that many industry commentators are saying that cyber security is now a top priority.
Are you fearful of migrating to a new data visualisation solution or hosting data in the cloud? The power of Power BI is too much to ignore and offers many security features to ease your concerns.
There have been a number of notable security vulnerabilities uncovered last month including some for Chrome and Magento, while Huawei remains in the limelight:
As January draws to a close, Microsoft lets in the new year with a CU for 2016 SP1 & SP2 and a hotfix for 2017 CU13 (as below). There are also Windows updates and a variety of stories in the news to take a look at.
As the year 2018 came to a close, we saw a few updates in regards to SQL Server, where Microsoft released Cumulative Updates for both SQL Server 2014 and 2017. Alongside this, there were also a number of Windows Updates released, which can be found below:
This November, Microsoft released Cumulative Updates for SQL Server 2016 SP1 and SP2. In addition, we have seen a number of Windows Updates released this month, see below for more details.