SQL Server 2014 Management tools

Management tools play a vital role in enterprise database management. This is because the well-integrated tools extend the administrator’s capabilities, whereas a random collection of tools can lead to confusion, operational mistakes, high training costs, and poor DBA productivity. To keep up with these demands of complex enterprise database management solutions, SQL Server 2014 includes updated management tools to make it easier for administrators to create, manage, and maintain SQL Server solutions.

Click here to read full article on SSWUG.org


SQL Server monitoring and optimization

To optimize the performance of your database, you need to monitor and tune. You determine the performance baseline, how SQL Server is currently performing, through monitoring. Your optimization process includes making changes and then monitoring their effect. This means adjusting two overlapping performance areas, that is, database server performance and query performance.

Click here to read full article on SSWUG.org

SQL Server Encryption Options

Many database servers store confidential data, which must be protected from unauthorized access when it’s transmitted across the network and stored on the server. SQL Server provides support for encrypted connections, encrypting data, encrypting database and for encrypted storage.

Click here to read full article on SSWUG.org

Bulk Transfers: Some guidelines

Bulk transfers are a common way of importing large amounts of data into, or exporting large amounts of data out of, SQL Server databases.  SQL Server supports bulk transfers run from an operating system command line or the SQL Server command processor. When performing bulk transfers, you must consider the implications regarding the impact on server performance, file sizes (especially for transaction log file), and data access.

Click here to read full article on SSWUG.org

Understanding Triggers

A trigger is a specialized stored procedure that activates (executes) in response to an event. There are two basic trigger types, ie data manipulation language (DML) trigger and data definition language (DDL) trigger, based on the type of event that causes them to fire. For example, a data manipulation language (DML) trigger fires in response to INSERT, UPDATE, or DELETE events on a specific table whereas a data definition language (DDL) trigger fires in response to a data definition event, such as creating or dropping an object.

DDL triggers can have a scope of a database or the server. DDL triggers were introduced as a new feature with SQL Server 2005. The scope of a DML trigger is a table. Earlier versions of SQL Server support only DML triggers.

Click here to read full article at SSWUG.org

Possible ways to secure SSIS Packages

SQL Server Integration Services (SSIS) security is based around several layers that provide a rich and flexible security environment. These layers of security include the use of digital signature, package properties, SQL Server database roles and operating system permissions.

Checkout my article here, in which I gave an overview of SQL Server Integration Services security, and explained these layers that enable us to assure our SSIS packages security.

This article is published on SSWUG.org.

Back to basics: Transact-SQL programming fundamentals – (Part 2)

In the first of this three-part series, you will learned how to use scripts and batches, and basics of T-SQL variables.

Checkout the part-2 of this article series here, you will learn about Transact-SQL control-of-flow language, including BEGIN…END, IF…ELSE, CATCH, WHILE, BREAK, CONTINUE, RETURN, and WAITFOR.

This article is published on SSWUG.org.