Chapter 6 - Administration and Active Directory Integration

Chapter 13 - Programming Tools and Technologies in SQL Server

Chapter 3 - Managing and maintaining an active directory infrastructure

Pro SQL Server Internals explains how different SQL Server components work under the hood and how they communicate with each other. This is the practical book with a large number of examples that will show you how various design and implementation decisions affect the behavior and performance of your systems. Pro SQL Server Internals covers a multiple SQL Server versions starting with SQL Server 2005 all the way up to the recently released SQL Server 2014. Youll learn about new SQL Server 2014 features including the new Cardinality Estimator, In-Memory OLTP Engine (codename Hekaton), and Clustered Columnstore Indexes. With Pro SQL Server Internals, you have a solid roadmap for understanding the depth and power of the SQL Server database backend, regardless of the version and edition of SQL Server you use. Pro SQL Server Internals does the following:Explains how to design efficient database schema, indexing, and transaction strategies. Shows how various database objects and technologies are implemented internally and when they should or should not be used. Demonstrates how SQL Server executes queries and works with data and transaction logs. What youll learnDesign and develop efficient database solutions utilizing SQL Server as the database backend. Troubleshoot and address design, concurrency, and performance issues in systems. Choose the right database objects and technologies for the job. Improve system availability and manageability and reduce implementation costs with data partitioning. Design efficient Disaster Recovery and High-Availability strategies for systems. Improve the performance of OLTP and Data Warehouse systems by utilizing new SQL Server 2014 features, such as the In-Memory OLTP Engine and Clustered Columnstore Indexes. Who this book is for Pro SQL Server Internals is a book for developers and database administrators who want to design, develop, and maintain systems in a way that gets the most from SQL Server. This book is an excellent choice for people who prefer to understand and fix the root cause of a problem, rather than applying a 'band aid' to it.

Welcome to part two of our miniseries on connecting SQL Server CE on the Pocket PC to SQL Server. In last night’s episode, you learned the tale of two SQL Servers that exchanged data with each other via a technology called RDA. Tonight you’re going to learn about another way to skin the same cat with SQL Server merge replication. Long before SQL Server CE was born, big brother SQL Server 7 and 2000 implemented a method of distributing data amongst remote servers called merge replication. Essentially this means that one SQL Server can make the contents of its databases and tables available to other SQL Servers by publishing those objects and the data contained in them. Other SQL Servers subscribe to those publications in order to create replicas of those objects and their data on their own servers. This is a great way to move the data that people need closer to them. One common example of this technology is a branch office that replicates with a home office so that branch users won’t have to run queries over the WAN. Today, SQL Server CE can take advantage of this same technology by subscribing to publications found in SQL Server. The replicated data can be added to, updated, and deleted, and then remerged back into SQL Server. This makes for a powerful alternative to RDA and will certainly help your field agents get their memos merged together in a unified SQL Server database back at headquarters.KeywordsServer AgentVisual BasicIdentity ColumnDatabase EngineRadio ButtonThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Unlike SQL Server, the Windows operating system uses preemptive scheduling to schedule and manage threads. Sometimes SQL Server has to use Windows functions to perform specific actions through the operating system, for instance, when checking Active Directory permissions. When this occurs, SQL Server will have to ask a thread from the Windows operating system, outside of SQL Server, thus making it impossible for SQL Server to manage that thread. While SQL Server is waiting for the preemptive thread inside the Windows operating system to complete, SQL Server will record a wait on a preemptive Wait Type.

The management and maintenance of SQL Server have witnessed significant advancements between 2015 and 2024, driven mainly by the growing complexity of database environments combined with the growing demands for systems that are highly available, secure, and high-performing. Throughout this period, several groundbreaking features were added, with the objective of making databases more scalable, efficient, secure, and manageable. Some of the major breakthroughs include advanced performance optimization techniques, automated software for regular maintenance tasks, and advanced security features such as Always Encrypted and Row-Level Security. Moreover, with the growing use of cloud computing, SQL Server has evolved towards hybrid environments, thus enabling greater flexibility and scalability through offerings such as Azure SQL Database and Azure Arc for hybrid deployments. Despite these advances, there are substantial research gaps, particularly in predictive maintenance, AI-optimized optimization, and the challenges of managing SQL Server environments in fast-evolving, containerized, and microservices-based environments. Additionally, as SQL Server evolves further, the need for seamless integration with future technologies like machine learning and big data analytics requires further research, particularly in PolyBase and SQL Server Machine Learning Services.

Microsoft Access (Jet) is a powerful relational database, and, as such, it provides a useful tool for those needing a desktop database. Many need more. Microsoft markets SQL Server Desktop Engine as an alternative to Jet for those instances when you need a database server that can be easily distributed and installed, and you don’t want to spend a lot of money. The SQL Desktop engine (known as MSDE 1.0 in Office 2000) is a data engine that’s based on core SQL Server tech­nology Basically, you’re getting the full-blown SQL Server engine with some limitations (which we’ll discuss later). In this chapter, we’ll view just what SQL Desktop is and who it services. Along the way, we’ll compare Access, SQL Desktop, and SQL Server features and requirements.

2 - Windows Security Authorities and Principals

Chapter 11 - Managing Active Directory Users, Groups, and Computers

8 - Business Intelligence

SQL Server 2014 is the latest release of Microsoft's enterprise-class database management system (DBMS). As the name implies, a DBMS is a tool designed to manage, secure, and provide access to data stored in structured collections in databases. Transact-SQL (T-SQL) is the language that SQL Server speaks. T-SQL provides query and data-manipulation functionality, data definition and management capabilities, and security administration tools to SQL Server developers and administrators. To communicate effectively with SQL Server, you must have a solid understanding of the language. In this chapter, you begin exploring T-SQL on SQL Server 2014.

This article describes the SQL Server object model SQL-DMO. Through the object model all information of SQL Server's internal objects can be obtained, including databases, data tables, stored procedures and triggers and so on. Analysis the method of the object’s information extraction. Get the child object by analyzing the parent object’s collection property and get internal information by analyzing the object’s properties. A visual basic procedure is designed to achieve the table’s structure information for all user tables in specified SQL Server database. This method is more complete and simple than the method based on system table.

Databases are an essential component of life in modern society. The database has become an online Transaction Processing (OLTP) operational support company. This study discusses the storage configuration in a virtual server database for OLTP Database with a benchmark against three storage configurations for four databases: SQL Server, MySQL, PostgreSQL, and MariaDB for Windows Server virtualization. Benchmarks using TPC-C to get the best performance from all three configurations have been tested. The results of this study show that the storage configuration of HDD as a virtual disk drive OS and NVME as a virtual disk drive database get better performance as online transaction processing (OLTP) compared to HDD as a virtual disk drive OS and HDD or SSD as a virtual disk drive database. Using the TPC-C benchmark, the study tested the performance of four databases (SQL Server, MySQL, PostgreSQL, and MariaDB) in various virtual storage configurations. The results of 36 experiments involving different numbers of virtual users (10, 50, and 100) showed that a hybrid configuration that used HDDs for the operating system and NVME for database storage provided the best performance. On SQL Server, SSD configurations show better results for smaller user loads. The results suggest that the combination of HDD and NVME is the optimal configuration for most databases in OLTP tasks, and it provides useful guidance in efficient storage investment decision-making. Further research is expected to be able to conduct tests.

The migration of Microsoft SQL Server databases from on-premise environments to cloud-based Infrastructure as a Service (IaaS) platform has become a strategic imperative for modern enterprises seeking agility, scalability, and cost-efficiency. This transformation leverages cloud computing’s pay-as-you-go model, enabling faster deployment, global reach, and enhanced resource optimization. This paper presents a comprehensive exploration of migration strategies, automation frameworks, and DevOps integration practices to support large-scale SQL Server transitions to leading cloud IaaS providers such as Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP). The analysis includes a comparison of native migration tools (e.g., Azure Database Migration Service, AWS DMS, GCP DMS), infrastructure-as-code solutions (Terraform, PowerShell), and database DevOps tools (Liquibase, dbForge, Redgate) to automate, streamline, and secure the migration lifecycle. Furthermore, the study examines the integration of SQL Server database changes into CI/CD pipelines, significantly reducing manual intervention and enabling consistent deployments across environments. Emphasis is placed on performance benchmarking, licensing models, cost optimization, and high availability architectures. Security concerns, including encryption, access control, and compliance requirements, are also thoroughly addressed. This research aims to equip IT leaders, database administrators, and enterprise architects with practical insights and frameworks to execute seamless, resilient, and cost-effective SQL Server migrations while maintaining operational excellence and business continuity.

Stored procedures are fixtures in the life of just about anyone who uses modern relational database systems such as Microsoft’s SQL Server. A stored procedure is a bit of code that lives on the database server and often acts as an abstraction layer isolating the code consuming the data from many of the details of the physical organization of the data. Stored procedures can increase performance by moving data-intensive computations closer to the data, and they can act as a data-side repository for business and security logic. The bottom line is that if you use data, you will consume it at some point through a stored procedure.KeywordsSales ManagerDesign SurfaceCustom FunctionReturn TypeEntity CollectionThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.