September 2019
• Checking the Version and Build Number of an SSIS Package
  
September 2018
• Checking Whether Connections to SQL Server are Encrypted
  
November 2017
• Amazon RDS - Common Issues with native SQL Server backup and restore
  
October 2017
• SQL BITS Conference - London 2018
  
February 2017
• SQL Server TCP Port vs TCP Dynamic Ports
  
January 2017
• Registered Servers vs Central Management Servers
  
November 2016
• Amazon RDS – Creating a native (.bak) Backup of a SQL Server Database in RDS
  
June 2016
• Searching ALL SQL Server Logs using TSQL
  
May 2016
• Pros and Cons of Transparent Data Encryption (TDE) Part 1 of 3
  
• Setting up Transparent Data Encryption (TDE) Part 2 of 3
  

SQL Matters is a resource for SQL Server Developers, Architects, DBAs and others interested in SQL Server and related technologies . Our site contains a wide range of articles, tips, blogs, quiz questions and other information about the SQL Server range of products. This includes Integration Services (SSIS), Reporting Services (SSRS), Analysis Services (SSAS) and some other products that we feel might be of interest to the SQL Server community such as PowerPivot and Report Builder.

Here are some examples of technical information that you might be interested in :

• Formatting a number with thousand separators
• Splitting the query window in SSMS
• Determining the last time SQL Server was started

By default a database has a single filegroup called PRIMARY and all tables are stored in this filegroup. However it’s possible to create other filegroups and store tables in these new filegroups. One of the most common reasons for doing this is if you have some high performance disks and want to store certain tables on those faster disks. This is especially useful for data warehouses and other large databases where you might have some data that is accessed more frequently and where response times are particularly important. This article shows how to create another filegroup and move existing tables into the new filegroup (if you are creating new tables then you can just create them on the new filegroup). I have used the AdventureWorks2008R2 demo database which can be downloaded from the CodePlex website.

The stored procedure xp_readerrorlog (and also sp_readerrorlog) allows searching of the SQL Server error logs. However only one log can be searched at a time. This script searches all available logs, by looping through each log in turn.

What is the result of the following SQL query ?
Choose one : a) 3    b) 6    c) 50    d) 100