This post is authored by Xiaochen Wu, Program Manager, SQL Server.
Azure SQL Data Sync allows users to synchronize data between Azure SQL Databases and SQL Server databases in one-direction or bi-direction. This feature was first introduced in 2012. By that time, people didn’t host a lot of large databases in Azure. Some size limitations were applied when we built the data sync service, including up to 30 databases (five on-premises SQL Server databases) in a single sync group, and up to 500 tables in any database in a sync group.
Today, there are more than two million Azure SQL Databases and the maximum database size is 4TB. But those limitations of data sync are still there. It is mainly because that syncing data is a size of data operation. Without an architectural change, we can’t ensure the service can sustain the heavy load when syncing in a large scale. We are working on some improvements in this area. Some of these limitations will be raised or removed in the future. In this article, we are going to show you how to use data sync to sync data between large number of databases and tables, including some best practices and how to
https://blogs.msdn.microsoft.com/sql_server_team/analyze-synchronous-commit-impact-on-high-commit-rate-workloads/Source: https://blogs.msdn.microsoft.com/sql_server_team/analyze-synchronous-commit-impact-on-high-commit-rate-workloads/ Recently the SQL Server Always On Support team at Microsoft CSS published a blog on analyzing the performance impact of Synchronous Commit AG’s with workloads that perform a large number of small transactions. For Synchronous AG’s every READ MORE
The world’s leading database is now available on Linux by bringing Microsoft SQL Server to Linux, Microsoft continues to embrace open source solutions.
SQL Server 2017 brings the best features of the Microsoft relational database engine to the enterprise Linux ecosystem, including SQL Server Agent, Azure Active Directory (Azure AD) authentication, best-in-class high availability/ disaster recovery, and unparalleled data security.
Note that SQL Server on Linux is not a port or rewrite. This is the same world-class Microsoft relational database management system (RDBMS) now available on more operating systems (like Red Hat Enterprise Linux, SUSE Linux Enterprise Server, and Ubuntu) and more cloud and container platforms (like Docker).
Join us for one or all of a three-part webcast series now available on demand as we explore how SQL Server 2017 brings the industry-leading Microsoft relational database engine to the enterprise Linux ecosystem with our partners from Intel, Red Hat and HPE.
SQL Server 2017 on Linux- #1 in price and performance—with massive scale
Learn how you can get record breaking performance with SQL Server on Linux. SQL Server consistently leads in the TPC-E OLTP workload, the TPC-H data warehousing workload, and real-world application performance benchmarks.
Customers today demand the latest innovations in every solution you deliver. How can you make sure your data infrastructure not only keeps up, but drives innovation?
Data is the core of modern applications. Two key trends that help organizations extract the most from their data are the adoption of cloud technologies and the ability to drive new customer experiences with artificial intelligence. Organizations that modernize and harness data, cloud, and AI outperform their competition and are becoming leaders in their field. The most digitally transformed enterprises earn an additional $100 million in operating income!
Join our speakers Claudia Backus, Prem Prakash, and Frederico Rezende for a webinar on how you can transform your applications and enable new customer experiences using the Microsoft data platform.
In this webinar, you’ll learn:
How to leverage the performance, security and flexibility of the entire Microsoft database portfolio from SQL Server 2017 and Azure SQL Database to open-source databases like Azure Database for MySQL and Azure Database for PostgreSQL. How to accelerate your move towards a cloud-based application with the new Azure Database Migration Service. How the Microsoft Data Accelerator program can help you modernize your apps across on-premise and cloud.
Register now for this
This blog post was authored by Alan Yu, Program Manager, Microsoft SQL Server.
We are excited to announce the January release of SQL Operations Studio is now available.
Download SQL Operations Studio and review the release notes to get started. SQL Operations Studio is a data management tool that enables you to work with SQL Server, Azure SQL DB, and SQL DW from Windows, macOS, and Linux. To learn more, visit our Github.
SQL Operations Studio was announced for public preview on November 15, 2017 at Connect(), and this January release is the second major update since the announcement. If you missed the December release announcement, you can learn more on the SQL Server blog.
The January release includes several major repo updates and feature releases, including:
Enable the HotExit feature to automatically reopen unsaved files. Add the ability to access saved connections from Connection Dialog. Set the SQL editor tab color to match the Server Group color. Fix the broken Run Current Query command. Fix the broken pinned Windows Start Menu icon.
For a complete list of updates, please refer to the release notes.
A highly requested feature for SQL Operations Studio is to remember
https://blogs.msdn.microsoft.com/sqlsecurity/2017/12/28/azure-log-analytics-oms-agent-now-collects-sql-server-audit-logs/Source: https://blogs.msdn.microsoft.com/sqlsecurity/2017/12/28/azure-log-analytics-oms-agent-now-collects-sql-server-audit-logs/ We are happy to inform that the Azure Log Analytics (OMS) Agent is now capable of pushing SQL Server audit logs into Azure Log Analytics (OMS), supporting SQL Server both on-premises, as well as on Azure VMs. READ MORE
This post is authored by Alan Yu, Program Manager, SQL Server.
We are excited to announce the December release of SQL Operations Studio is now available.
SQL Operations Studio is a data management tool that enables you to work with SQL Server, Azure SQL DB and SQL DW from Windows, macOS and Linux. To learn more, visit our GitHub.
SQL Operations Studio was announced for Public Preview on November 15th at Connect(), and this December release is the first major update since the announcement.
The December release includes several major repo updates and feature releases, including:
Migrating SQL Ops Studio Engineering to public GitHub repo Azure Integration with Create Firewall Rule Windows Setup and Linux DEB/RPM installation packages Manage Dashboard visual layout editor “Run Current Query with Actual Plan” command
For complete updates, refer to the Release Notes.
Migrating SQL Ops Studio Engineering to public GitHub repo
To provide better transparency with the SQL Operations Studio community, we have decided to migrate the Github internal branch to the public repo. This means any bug fixes, feature developments, or even test builds can be publicly viewed before an
SQL Server 2017, in addition to processing relational data, now fully integrates with graph database models, all on the same familiar system. This will bring clarity to the increasing amounts of data businesses generate every day.
What’s the difference between graph and relational databases?
Relational databases, like SQL Server, use foreign keys to manage relationships between entities and tables. Foreign keys adequately query one-to-many relationships; however, as relationships between various data entities become more complex, queries also become more complex and performance may diminish as a result.
In these cases, developers may opt for graph database models to manage complex relationships and enable operational agility. In a graph database, edges are heterogeneous in nature—a single edge can be used to connect different type of nodes to each other. This is not easy to achieve using foreign keys in a relational database. For example, consider a social graph where a person (node) likes another person (edge) or organization (node) or restaurant (node). Here the same ‘likes’ edge is used to connect three different types of nodes and entities to each other—person to person; person to organization; and person to restaurant.
So, how do graph databases work?
Graph databases are comprised of a
This post is authored by Alan Yu, Program Manager, SQL Server.
We are excited to announce the Public Preview release of mssql-cli, a new and interactive command line query tool for SQL Server. This open source tool works cross-platform and is a proud member of the dbcli community.
See the install guide to download mssql-cli and get started.
Read on to learn more about mssql-cli features, how to submit feature requests or issues, and our open source collaboration story to bring you this great tool.
mssql-cli auto-completion that is context aware
Mssql-cli is a new and interactive command line tool that provides the following key enhancements over sqlcmd in the Terminal environment:
T-SQL IntelliSense Syntax highlighting Pretty formatting for query results, including Vertical Format Multi-line edit mode Configuration file support
Mssql-cli aims to offer an improved interactive command line experience for T-SQL. It is fully open source under the BSD-3 license, and a contribution to the dbcli organization, an open source suite of interactive CLI tools for relational databases including SQL Server, PostgresSQL, and MySQL. The command-line UI is written in Python and the tool leverages the same microservice backend (sqltoolsservice) that powers the VS Code SQL extension,
https://blogs.msdn.microsoft.com/sql_server_team/centennial-appsdesktop-bridge-sql-server-and-error-the-data-area-passed-to-a-system-call-is-too-small/Source: https://blogs.msdn.microsoft.com/sql_server_team/centennial-appsdesktop-bridge-sql-server-and-error-the-data-area-passed-to-a-system-call-is-too-small/ The title of the blog may throw someone off a little. After all, SQL Server is not a centennial app and the error message doesn’t appear to have anything to do with SQL Server. So please bear READ MORE