Archive for the ‘SQL’ category

SQL Server 2016 SP2 CU10 – (it fixes CU 9)

October 10th, 2019

SQL Server 2016 SP2 CU10 is essentially a fixed version of CU9.

Microsoft added a note to the KB article to holdoff on CU9, and now…that CU9 KB article page has vanished altogether.

So CU9 is dead to Microsoft, Everything we said about CU9, is replaced by CU10.

SQL Server 2016 Service Pack 2 SP2 CU9 release

October 1st, 2019

Cumulative Update package 9 (CU9) (build number: 13.0.5470.0) for Microsoft SQL Server 2016 Service Pack 2 SP2 is now aavilablefor download. (It contains fixes that were released after the initial release of SQL Server 2016 SP2.)
SQL Server CUs are certified to the same levels as Service Packs, and should be installed at the same level of confidence. Historical data shows that a significant number of support cases involve an issue that has already been addressed in a released CU.

The CU provides the following fixes and improvements (Referenced from https://support.microsoft.com/en-us/help/4100997/cumulative-update-9-for-sql-server-2016-sp1)

KB4099472 – PFS page round robin algorithm improvement in SQL Server 2016 SQL service
KB4133164 – FIX: Error when a SQL Server Agent job executes a PowerShell command to enumerate permissions of the database Management Tools
KB4086173 – FIX: Access violation occurs when executing a DAX query on a tabular model in SQL Server Analysis Services Analysis Services
KB4131193 – Performance issues occur in the form of PAGELATCH_EX and PAGELATCH_SH waits in TempDB when you use SQL Server 2016 SQL service
KB3028216 – FIX: A crash occurs when proactive caching is triggered for a dimension in SSAS Analysis Services
KB4135113 – FIX: Change tracking record is inconsistent during an update on a table which has a cluster/unique index in SQL Server SQL service
KB4293839 – FIX: TDE database goes offline during log flush operations when connectivity issues cause the EKM provider to become inaccessible in SQL Server SQL security
KB4230730 – FIX: A dead latch condition occurs when you perform an online index rebuild or execute a merge command in SQL Server SQL service
KB4163478 – FIX: An access violation occurs when incremental statistics are automatically updated on a table in SQL Server SQL performance
KB4230306 – FIX: Restore of a TDE compressed backup is unsuccessful when using the VDI client SQL service
KB4163087 – FIX: Performance is slow for an Always On AG when you process a read query in SQL Server SQL service
KB4164562 – FIX: Wrong user name appears when two users log on to MDS at different times in SQL Server Data Quality Services (DQS)
KB4094893 – FIX: Database cannot be dropped after its storage is disconnected and reconnected in SQL Server SQL service
KB4162814 – FIX: An internal exception access violation occurs and the SSAS server stops responding Analysis Services
KB4134541 – FIX: Error in the MDS Add-in for Excel when you use the German version of Excel in SQL Server Data Quality Services (DQS)
KB4132267 – FIX: Deploying a SSAS project in SSDT is frequently unsuccessful in SQL Server Analysis Services in Tabular mode Analysis Services
KB4101554 – FIX: Parallel redo in a secondary replica of an availability group that contains heap tables generates a runtime assert dump or the SQL Server crashes with an access violation error High Availability
KB4098762 – FIX: Hidden parameters are included in reports when the Browser role is used in SSRS 2016 Reporting Services
KB4134175 – FIX: Processing a cube with many partitions generates lots of concurrent data source connections in SSAS Analysis Services
KB4091245 – FIX: Access violation occurs when you query a table with an integer column in SQL Server 2017 and SQL Server 2016 SQL performance
KB4094706 – FIX: One worker thread seems to hang after another worker thread is aborted when you run a parallel query in SQL Server SQL service
KB4058175 – FIX: TDE enabled database backup and restore operations are slow when the encryption key is stored in an EKM provider in SQL Server SQL service
KB4131960 – FIX: An access violation occurs when you execute a nested select query against a columnstore index in SQL Server SQL Engine
KB4094858 – FIX: “An unexpected error occurred” when you use DAX measures in Power BI table visualizations in SQL Server Analysis Services
KB4101502 – FIX: TDE enabled database backup with compression causes database corruption in SQL Server 2016 SQL service

CUs also often include supportability, manageability, and reliability updates.

Before udpate:

- Check compaitbiltiy with your application.
- Test CUs before you deploy to production environments.

SQL Server 2016SP2 Cumulative Update 8

August 3rd, 2019

The urgent security update earlier this month is not the only patch for SQL Server 2016 in July,
Microsoft has released SQL. SP2 CU8 (build number: 13.0.5426.0)
• Restores of compressed encrypted backups fail
• Data masking doesn’t
• DAXquery needs memory 200x larger than the database size
• Peer-to-peer replication fails when your host name isn’t uppercase
• QueryStore cleanup can fill the transaction log and cause an outage
•DistributedAvailability Groups cause memory dumps when automatic seeding
• AGreplication stops working due to internal thread deadlocks
•The deadlock monitor can cause an access violation
• Query a view with a union on a linked server,
• Concurrent inserts into a clustered columnstore index can deadlock
•Infiniteloop when FileTable is used for a long time without a restart
•SSAS2016 randomly crashes ( maybe not completely random if they fixed it)
•TransparentData Encryption doesn’t encrypt if it’s restarted mid-encryption

And much more.https://support.microsoft.com/en-us/help/4505830/cumulative-update-8-for-sql-server-2016-sp2

I guess we will get a similar patch for Sp1 but by now you should be on a later patch

SQL Server 2014 Sp3 mainstream support ended on July 9 – CU4 just released

July 31st, 2019

However Cumulative Update 4 for SQL Server 2014 SP3 has just been released.

https://support.microsoft.com/en-us/help/4500181/cumulative-update-4-for-sql-server-2014-sp3

SQL Server 2008 and SQL Server 2008 R2 -OUT OF SUPPORT today

July 13th, 2019

SQL Server 2008 and 2008 R2, both of these versions of SQL server go out of extended support with Microsoft today 9th July 2019

Many companies and businesses are still SQL Server 2008 R2 and below. There can be a number of reasons for this, maybe the applications the databases support require an older version of SQL Server, maybe the applications are also coming to the end of life, but the end dates do not match up with the data platform end of support dates.

Sometimes applications are critical to the business and everything works just fine. The business doesn’t want to disrupt the application or introduce any risk by performing a migration to a new version so why change it?

In this situation your data platform is out of support completely. Out of support system attract hackers. Note the previous articles about fines for loss of privacy data to realise how serious this can be

So you should be making plans to migrate your legacy SQL Servers off the unsupported versions. It is likely if you are still on an old database that you are also on an old server and on an old version of Windows. That gives additional risk of failed hard disks, other system vulnerabilities – Meltdown, Spectre? Phishing…….
Investors and insurers are not likely to be sympathetic in such circumstances.

There are many performance and security benefits of upgrade.

If you decide to run on out support software and take the risk associated with running on out of support software. The main advantage of this approach is there is nothing immediate to do. The longer you run on the platform the greater the chances of you encountering a security vulnerability or failing a compliance test.
If anything does go wrong you’ll have no support from Microsoft.
Other software vendors support contracts may also require that you be on a currently supported database

Modernise and upgrade is one of the options that you have available.

You can upgrade your on premises SQL Server or migrate the databases to Azure either as IaaS solution where you run the VM in Azure or even the PaaS Azure SQL database offering

There are number of advantages to upgrading your data platform. You’ll be running your database workloads on an in support data platform, with a long support window. There will likely by new features in the latest and greatest version of SQL Server that you can use to add business value to your application – Availability Groups for example. Also you will likely find people with skills in the later technology, those skills will be more readily available in the jobs market.

There will likely be a different licensing model – the licensing model changed between SQL Server 2008 R2 and SQL Server 2012 – it possible you will have to pay more for you SQL Server licences.

The third option is instead of doing nothing you pay for a custom support agreement. The main advantage here is you can continue to get security updates and therefore potentially remaining compliant. The main disadvantage of this approach is the cost involved, which is typically 75% of the full license costs of the latest version of SQL Server and Windows Server.

Migrate workload to Azure. Microsoft allow SQL Server 2008 and SQL Server R2 VMs running in Azure to have the security updates for free for a further 3 years. So you can migrate your database server to azure and continue to get security updates for free until 2022.

The main advantage of this is you get to keep running the same version of the OS and Data platform, the security updates are free so the cost is minimal \. The disadvantages is you would need to move off premises, if this is not an option for you then you can’t exercise this option and there will still be work in involved in ‘lifting and shifting’ the VM to the cloud.

Whatever you do when support ends for SQL Server 2008 and SQL Server 2008 R2 have a plan

SQL Server 2008 and SQL Server 2008 R2 – end of life July 9, 2019 -ask Synergy Software Systems

June 23rd, 2019

Microsoft has previously announced that SQL Server 2008 and SQL Server 2008 R2 will reach end of life on July 9, 2019.

This means that in less than a month, Microsoft will no longer release regular security updates for the product.

There are several reasons this is important to you.
• Attacks against software products of all types are common and ongoing. With Microsoft SQL being such a prevalent platform, attacks against it are ubiquitous, and it’s important to keep your database platform up-to-date with the latest Microsoft security patches.
• Many compliance requirements dictate that you must be running currently supported software.
• As Microsoft drops support for a product, many third-party applications may also discontinue support for their products running on those platforms.

So, if you are still running SQL Server 2008/2008 R2, then what are your options?

1.Upgrade to a newer version of SQL.
SQL 2019 is in preview release as of this writing, so the current production version of SQL Server is 2017. Its end of life will be October 12, 2027.
Evaluate your applications and databases to make sure they are compatible e.g. Dynamic Ax 2012 is not supported beyond SQL 2016

Plan a migration for either on-premises or cloud. A move to an Azure SQL Database Managed Instance, will not require you to upgrade in the future. By choosing this option, you will also gain access to new features which have appeared in the latest SQL Server versions. However, it only offers subset of SQL features so you need to be sure it will support your application and use.

2.Migrate to Azure to receive three more years of Extended Security Updates for SQL Server 2008/2008 R2. If you need to stay on the same SQL code base for a bit longer, Microsoft will allow you to rehost your SQL 2008 environment in Azure and still provide you with security updates for an extended period. There is no extra cost for the extended updates beyond the standard Azure VM rates.

3.Purchase extended support. Microsoft allows customers with an active Enterprise Agreement and Software Assurance subscription to purchase and receive three years of Extended Security Updates for SQL Server 2008/2008 R2. The annual outlay for the updates is 75% of the full license cost.

4.The least desirable option is to stay where you are and pray. If circumstances prevent you from moving forward now, then at minimum you should:
• Recognize and account for the risk;
•Plan and budget for a transition as soon as possible;
•Re-evaluate your security and tighten it as much as possible.

Microsoft provides guidance for handling the end of support of SQL Server 2008/2008 R2 at https://www.microsoft.com/2008-eos.

Of course, Synergy is ready to help you to evaluate and to progress to the next level. 0097143365589

If you are running newer versions of SQL Server, then here are their End-of-Life dates.
•SQL Server 2012 – July 12, 2022
•SQL Server 2014 – July 9, 2024
•SQL Server 2016 – July 14, 2026
•SQL Server 2017 – October 12, 2027

Windows Server 2008 and 2008 R2, support is coming to an end.

June 23rd, 2019

Sometimes lifecycles end because of age or workload and other times they expire due to vendor support.
In the case of Windows Server 2008 and 2008 R2, Microsoft announced that Extended Support will end on January 14, 2020.

Microsoft provides: Mainstream Support, Extended Support, and Beyond End of Support.

Mainstream Support

Mainstream Support is Microsoft’s first phase of support and lasts five years. It includes the following benefits:
• Incident support (no-charge incident support, paid incident support, support charged on an hourly basis, support for warranty claims)
• Security update support
• Ability to request non-security updates

Extended Support

The Extended Support phase follows Mainstream Support, and also lasts five years. The key features of Extended Support are:
• Paid support
• Security updates at no additional cost
• Ability to request non-security updates (available only via Unified Support, a new model of support that offers comprehensive support that covers your entire organization)
• Microsoft will not accept requests for warranty support, design changes, or new features during the Extended Support phase.

Beyond End of Support

The Beyond End of Support phase is the final phase of the product lifecycle and lasts for three years. Here are the key things to remember.
• Request to change product design and features are not available
• Security updates are available only with the purchase of the Extended Security Update Program for up to three years. This typically costs 75% of the on-premises license cost annually.
• Technical support is provided when you purchase Extended Security Updates and have an active support plan in place on the product that has moved beyond the Extended Support date.

Server 2008 and 2008R2 are moving out of the Extended Support phase on January 14, 2020. From that date on,
non-security updates will no longer be available,
security updates will be available only if you pay for the Extended Security Update Program,
and other vendors will diminish their support of this operating system version.
If you are not prepared, then this will leave your environment open to security holes, application instability, and support restrictions.
If you have not already planned for this then now is the time to get it into your budget for first thing next year.

Summer discount on SQL protection tools

June 18th, 2019

Security, privacy, performance, and up time, all depend on a well maintained database with timely reports and alerts.
for an Enterprise system this is mission critical.
Few DBAs have the time and training to write and maintain a comprehensive set of scripts. Yet they also often lack the tools to do the job.
We offer fantastic suite of tools to help you to mange your SQL databases and with discounted bundled prices.
With privacy laws and compliance adding to the ever rising security threats, a well managed system is now often key to whether a customer will share data it you, and directly impacts whether you can secure and retain business.

Talk yo us about System health checks and administrator training, and how you can reduce administrative cost, and system risks with SQL management tools.
00971 43365589

Major SQL updates don’t skip – SQL Server 2016 SP2 CU7 and SQL Server 2017 CU 15

May 26th, 2019

This week, Microsoft released two major updates.

SQL Server 2016 SP2 CU7 has multiple fixes including:

• Filtered index corruption
• Access violations in sys.dm_exec_query_statistics_xml, sys.dm_hadr_availability_replica_states, sys.availability_replicas, sys.dm_db_xtp_hash_index_stats, sys.fn_dump_dblog, sys.dm_db_xtp_checkpoint_files
(I.e. if you monitor your servers, which you should, then you should apply this CU to avoid problems caused by the monitoring tool’s queries)
• AG failover fails
• Incorrect query results on columnstore indexes, and also this

SQL Server 2017 CU 15 has even MORE fixes, read the full list. https://support.microsoft.com/en-us/help/4498951/cumulative-update-15-for-sql-server-2017

Note also, that from SQL Server 2017, the Analysis Services build version number and SQL Server Database Engine build version number do not match

There are some CUs you might be tempted to skip because they don’t affect you. These releases will affect a wide range of features and you should plan to apply these sooner than later.

SQL 2014 updates April 2019

April 18th, 2019

SQL Server 2014 seems to have become a lot more stable i.e this shot list is the entire list of fixes in Service Pack 3, Cumulative Update 3:
• Query plans are different on cloned databases
• CDC source preview fails with an error
• Incorrect query results for columnstore filter pushdowns
• Log reader agent fails after AG failover when trace flag 1448 is enabled

And for the entire list of fixes in Service Pack 2, Cumulative Update 17:
• SQL jobs fail due to blocking in SSISDB
• Fail to join the secondary replica if the database has a defunct filegroup
• Incorrect query results for columnstore filter pushdowns

Power BI update March – April 2019

March 21st, 2019

Microsoft launched the public preview of new Power BI workspace experiences in August 2018 to enable Power BI workspace admins:
• to use security groups to manage access to workspaces,
• to enable BI teams to create workspaces without needing to create an Office 365 Group,
• to provide granular workspace roles to make giving access to workspaces easier.

At the beginning of April 2019, the new workspace experiences. will reach General Availability (GA)

Usage metrics for new workspaces are rolling out this week
This capability is much requested by customers and works the same as it did for classic workspaces based on Office 365 Groups. It may take until late this week or next week to reach all commercial cloud customers.

https://powerbi.microsoft.com/en-us/blog/update-on-the-new-workspace-experiences-preview-including-ga-timeline/

The March update for the On-premises data gateway (version 3000.2.47) includes an updated version of the Mashup Engine, which matches the one released as part of the Power BI Desktop March update.

This will ensure that the reports that you publish to the Power BI Service and refresh via the Gateway will go through the same query execution logic/runtime as in the latest Power BI Desktop version.

Happiness Day, Loneliness and Power BI

March 21st, 2019

At the annual Gartner BI Bake Off session at the Gartner Data and Analytics Summit in Orlando, Florida the Power BI team featured this report which you can explore here:

Here are some insights and highlights from the report:
• The employment groups with the most happiness are employed and retired people followed closely by stay at home parents and students.
• The highest ratio of lonely to non-lonely people by age group is between 35 and 44 years old.
• For the countries in the dataset, the UK and the US have higher loneliness ratios (0.30 and 0.29 respectively) than Japan (0.10).

if you think Power BI might provide insights into your business, and need training or assistance with report modelling, or need to understand the different licence types, then contact us – 009714 3365589

SQL 2016 SP2 CU6 is released also SQL 2016 SP1 CU 14

March 21st, 2019

The good news is that Microsoft has fixed the “String or binary data would be truncated” error!
With KB#4468101 if you enable trace flag 460, the SQL Server will now tell you just what l is going to be truncated.
SP2 CU6 also includes other fixes like:
• Users are incorrectly permitted to create incremental stats on nonclustered indexes that aren’t aligned to the base table
• Assertion for parallel deletes from filestream tables
• Filestream IO can’t be enabled on cluster shared volumes
• Assertion for linked server queries that point to themselves during a cross-database transaction (as bad as it sounds)
• MDS database upgrade fails
• Filtered nonclustered columnstore index over a clustered columnstore index may not be maintained ( in layman’s term we call it corruption)
• Stack dump during change tracking cleanup
• Data masking (doesn’t)

Microsoft also released an 2016 SP1 CU14 but that doesn’t have the key#4468101 fix. .

Cloud back ups or on-premise?

February 16th, 2019

Pretty scary.
We have suffered catastrophic destruction at the hands of a hacker, last seen as aktv@94.155.49.9 This person has destroyed all data in the US, both primary and backup systems. We are working to recover what data we can.

Though they’re back up and running, who knows if customers will stick by them, or will sue them.
What impact that had on infrastructure mail servers, backup servers, and SQL Servers for customers is hard to judge.
A large number of people might have lost their mailboxes and previously stored mail that was in IMAP storage.
This is likely an annoyance for individuals, but potentially catastrophic for businesses. Imagine your small business hosted with them and all your mailboxes were lost with customer communications and who knows what else.

Could this happen with a cloud provider like Azure O365, Google Apps or AWS?
Maybe but they will have DR backups,
But what if you store back ups on the cloud but run on premise- how long would it take to mass restore multiple, customers? Do you still have ad3qute on premise test systems to restore on and the staff and the time to do it?

Do you assume that you will always have either a primary server and an online backup server/share/bucket/container and can download data.
The problem is that online systems that connect to the primary can be accessed.
If an attacker were to access one, they potentially could access the second.
The world seems to be moving towards more online storage, or in the case of cloud vendors, a reliance on snapshots. That might be good enough for cloud vendors, but is it good enough for your on-premise system.
It’s likely that an attacker, possibly even with insider help, would wipe out backups first, then primary systems.
Some sort of disconnected offline backup of data, especially database servers gives you a third line of defence.
don’t forget that back up- need to be tested- if the back up software compatible with old versions, does your back up use the same version as the current erp software installed on your primary, or the same SQL version (i.e when you upgrade do you also upgrade your back ups, or maintain an older environment?)

Microsoft and other large vendors have had downtime whether self induced by releasing code too early, or due to hardware failure, or malicious attach . What is important to realise is just how infrequent are just issues given the number of clients they have across a range of solutions, and how little was the downtime and how fast they are at in addressing issues that arise. The think about how you would have been able to deal with the same issues in your own server room?

There are increasing risks, and increasing issues of statutory compliance with regard to data protection e.g, GDPR. The cloud generally offers cheap storage nd robust systems, yet it needs to be part of a holistic approach to reduce overall risk and cost, and not the only line of defence.

SQL Server 2016 SP2 CU5, SP1 CU13 – many fixes

January 25th, 2019

Many fixes inside SP2 CU5 and SP1 CU13, e.g.:
• Access violation when you compile a query
• Access violations and unhandled exceptions with Always On Availability Groups automatic seeding
• Dynamic Data Masking doesn’t when there’s a cursor involved
• Access violations for XML data types
• Query Store blocks transactions and log truncation
• Out of memory errors
• Non-yielding schedulers with heavy use of prepared statements
• Can’t restore compressed backups of encrypted databases
• High CPU usage when there are many batch requests (which we would expect?)
• SQL Server service crashes when you cancel CHECKDB (on a “large database” – doesn’t that apply to all? )
…. lots more