Tag: sql server 2016

Using SQL Server 2016 Upgrade Advisor

Kenneth Igiri Leave a comment
Total: 6 Average: 4

INTRODUCTION

SQL Server is designed to allow multiple databases on a single instance. With this model it is possible to have databases sitting on an instance which are not the same version as the instance itself. You can think of this as running the database in the “backward compatibility mode.” To break it down further, we are saying that you can have a 2008 database deployed on an SQL Server 2016 instance. In such a scenario, the database is, for instance, allowed to use certain constructs that belong to a previous version of SQL Server.

Read More

How to Use Semantic Search in SQL Server

Haroon Ashraf Leave a comment
Total: 23 Average: 4.5

This article deals with the basics of Semantic Search, including a complete walkthrough of Semantic Search: starting from scratch and finishing with a ready-to-use feature.

Additionally, the readers are going to learn about some of the very useful but not generally known Search features available in SQL Server like Semantic Search, which we’ll demonstrate with some basic examples.

Read More

Implementing Full-Text Search in SQL Server 2016 for Advanced Users

Haroon Ashraf Leave a comment
Total: 19 Average: 3.6

This article tells about advanced methods of Full-Text Search usage for data professionals. It enables better search experience in their day-to-day database analysis.

Additionally, the readers will get beyond basic knowledge of Full-Text Search and its implementation. You will see the importance of advanced searching methodology using Full-Text Search to get quick and reliable results.

Prerequisites

First, let’s go through prerequisites since the article is focused on advanced uses of Full-Text Search.

T-SQL Know-How

The article assumes that to implement the walk-through(s), the readers are familiar with writing and running T-SQL scripts against databases with a basic understanding of SQL Server. Read More

Implementing Full-Text Search in SQL Server 2016 for beginners

Haroon Ashraf 1 Comment
Total: 21 Average: 3.7

This article talks about the full-text search and its implementation for the beginners to get started.

Additionally, the readers will know the important things to make the full-text search work properly.

This article also highlights the importance of using Full-Text Search to match text patterns and meet similar sorts of requirements.

About Full-Text Search

Let’s understand the Full-Text Search with the help of definitions.

Simple Definition

Full-Text Search is used to optimally search character-based data for quick answers.

Microsoft Definition

Full-Text Search in SQL Server and Azure SQL Database (cloud version of SQL database) let users and applications run full-text queries against character-based data in SQL Server tables. Read More

In-depth Exploration of Row Level Security

Kenneth Igiri Leave a comment
Total: 4 Average: 4.3

Introduction

Organizations are becoming more and more concerned about how to reduce the cost of licensing database solutions using consolidation. Some consolidation can be achieved in SQL Server simply by taking advantage of the existing one-to-many relationship between instances and databases. However, there are cases where the solution demands that data is consolidated into one table. In such a case, there may be concerns about how to restrict access to the data.

Row Level Security was introduced in SQL Server 2016 as a solution to scenarios similar to the above. It allows you to restrict access to rows in a table based on conditions defined in an inline Table Valued Function called a Predicate Function. When a Predicate Function is applied to a user table containing consolidated data, the system can be configured to return different data sets to different users depending on their roles which in turn depends on their job descriptions or departments for example.

Read More

Introduction to Row-Level Security in SQL Server

Ben Richardson Leave a comment
Total: 8 Average: 3.5

Problem

Prior to SQL Server 2016, table-level security was the default lowest level of security for a database. In other words, a user could be restricted to access a table as a whole. However, in some cases we need users to have access to a table, but not to specific rows within the table. Prior to SQL Server 2016, this required custom stored procedures to be written for the provision of such fine-grained security. However, such stored procedures are prone to SQL injection and other security caveats.

Read More

Traditional and Natively Compiled Scalar-Valued User-Defined Functions

Esat Erkeç Leave a comment
Total: 19 Average: 4.1

In the software programming world, there are several approaches used by developers that help them with effortless software development. Design patterns, object-oriented programming, test driven development are some of them. If we particularly mention the code reuse; “Reuse of a typed code. It is written once and can be used in most places. It is a basic concept of software engineering. It is a structure necessary for modular programming. ”

For this reason, user-defined functions in SQL Server help us to avoid rewriting of T-SQL queries. At the same time, they improve code readability. In this post, we will discuss the pros and cons (advantages and disadvantages) of the traditional and natively compiled scalar user-defined functions and make a simple performance test.

Read More

Compare Execution Plans in SQL Server

Esat Erkeç Leave a comment
Total: 17 Average: 3.9

Database Administrator always makes an effort to tune SQL Server query performance. The first step in tuning query performance is to analyze the execution plan of a query. Upon some conditions, SQL Server Query Optimizer can create different execution plans. At this point, I would like to add some notes about SQL Server Query Optimizer. SQL Server Query Optimizer is a cost-based optimizer that analyzes execution plans and decides the optimal execution plan for a query. The significant keyword for the SQL Server Query Optimizer is an optimal execution plan which is not necessarily the best execution plan. That’s why, if SQL Server Query Optimizer tries to find out the best execution plan for every query, it takes extra time and it causes damage to SQL Server Engine performance. Read More