2021-09-08
765 reads
2021-09-08
765 reads
SQL Server 2008 and SQL Server 2008 R2 are out of extended support as of July 2019, but the end of bug fixes, security updates and ongoing support has far-reaching data privacy implications, as James Boother from Microsoft Gold Partner, Coeo, explains
2019-09-03
Your company is ignoring the news: SQL Server 2008 and 2008R2 are officially out of support as of today, but nothing’s changing at your company. You still have SQL Server 2008 in production, and you’re a little nervous. How should you approach the conversations with management? Brent Ozar will help: he;s been there too.
2019-08-02
Many organisations still run their companies on SQL Server 2008 or 2008 R2. There are many reasons to upgrade, but the most pressing reason is that extended support is running out. In this article, Brian Kelley explains what this means, tells you about some of the features you’ll gain if you upgrade, and provides some options.
2019-07-11
Support for SQL Server 2008 and 2008 R2 ended yesterday. Steve has a few thoughts on what you should be thinking about today.
2019-07-10
295 reads
2014-10-30
1,677 reads
After performing an update on SQL Server, SQL Server Engine and SQL Agent stop responding.
2014-08-26
3,047 reads
Generates Scripts to move DB files from one location to another SQL and powershell scripts
2016-04-11 (first published: 2014-03-19)
4,181 reads
Change Data Capture (CDC) records DML operations performed on SQL tables and makes records available with information regarding what changed and when the change happened in a simple way.
2013-06-24
7,245 reads
Transaction Replication Publisher failover/failback to mirror standby with automatic redirection of the subscriber and client application.
2012-06-28
2,795 reads
By Steve Jones
This is my last week of the year working (I guess I come back...
By Steve Jones
suente– n. the state of being so familiar with someone that you can be...
Anyone (everyone?) who has ever tried to learn a programming language knows that to...
I am getting the below error when I execute a SQL command in SQL...
I am getting the below error when I execute a SQL command in SQL...
Hi everyone. I have this table and this information. (left side of the image)...