Linked server to MySQL Server.
In this article, we are going to create a linked server to the MySQL Database.
Once finished that task, we will select, insert, update and delete some data using SQL Server.
The Best of the Best
Today's editorial was originally pubished on June 26, 2007. It is being re-run today as Steve is traveling. What were the best places to work in 2007? Steve Jones links to a list and talks about the value of using those lists.
Understanding Retention Periods for SQL Server Transactional Replication
I have transactional replication configured in production. I have heard about the replication retention period, but what is the significance of this. Would there be any impact to my replication configuration if data is not synchronized with the subscriptions within the retention period?
Big Data
Are you prepared for Big Data? A short piece from Henrico Bekker that talks about what Big Data might mean to many people.
Open Source Software and Cacoëthes Scribendi
Phil Factor on the irresistible urge to write code in the public domain, and the occasional desire to be free from the snails-trail of software that needs maintainence.
TSQL Challenge 80 - Find the minimal set of intervals without gaps
The challenge is to find the minimal set of intervals without creating gaps.
Migrating SQL Reporting Services to a new server
I need to move all the objects off the 2005 Reporting Server to the 2008 Reporting Server. Is there an easy way to do this without saving each report file (edit report and save .rdl) then uploading the report to the new server? This would also mean recreating the data sources and subscriptions.
Key Storage
Today Steve Jones asks about how you secure the keys that secure your other data. Is there a good way that you've found to handle this?
Sequences in SQL Server 2012
This article describes the sequence new feature used in SQL Server 2012
Migration Guide: Migrating to SQL Server 2012 Failover Clustering and Availability Groups from Prior Clustering and Mirroring Deployments
This paper provides guidance for customers who prior to SQL Server 2012 have deployed SQL Failover Clustering for local high availability and database mirroring for disaster recovery, and who want to migrate to SQL Server AlwaysOn. It describes the corresponding SQL Server AlwaysOn scenario and the migration paths to SQL Server AlwaysOn. It also contains the important knowledge and considerations that you must know in order to successfully migrate to a HADR solution based on SQL Server AlwaysOn technology, which implements AlwaysOn Failover Cluster Instances for high availability and AlwaysOn Availability Groups for disaster recovery.
Blogs
Flyway Tips: AI Generating Migration Script Names
By Steve Jones
AI is a big deal in 2026, and at Redgate, we’re experimenting with how...
The Book of Redgate: Get the right stuff done
By Steve Jones
Another of our values: The facing page has this quote: “We admire people who...
Runing tSQLt Tests with Claude
By Ed Elliott
Running tSQLt unit tests is great from Visual Studio but my development workflow...
Forums
No Defaults Passwords Ever
Comments posted to this topic are about the item No Defaults Passwords Ever
Introduction of OPTIMIZE_FOR_SEQUENTIAL_KEY = ON
Hi, We have low latency high volume system. I have a table having 3...
The Long Name
Comments posted to this topic are about the item The Long Name
Question of the Day
The Long Name
I run this code to create a table:
When I check the length, I get these results:
A table name is limited to 128 characters. How does this work?