Explore information related to mssql


SQL Server Error 19471: Create failed for Availability Group Listener


This article covers methods to fix SQL Server Error 19471. Basically,  "SQL Server Error 19471" can happen while configuring Always On Availability Group again on the database server.


To fix SQL Server Error 19471:

  • Create a Client Access Point (CAP) for the AOAG listener in Failover Cluster Manager.
  • Bring CAP Online.
  • Repair the CAP, if it is not coming ONLINE.
  • Once CAP comes online, remove it from failover cluster manager.
  • Add listener to AOAG in SSMS.

Read More



SQL Server Error 9002 - Fix it now


This article covers methods to resolve SQL Server Error 9002 for our customers. SQL Server Error 9002 happens when the SQL Transaction Log file becomes full or indicated the database is running out of space. A transaction log file increases until the log file utilizes all the available space in disk. A quick fix is to create more space for log file.


To Fix SQL Server Error 9002:


1. Backup Transaction Log File

Incase, SQL database that you are using is full or out of space, you should free the space. For this purpose, it is needed to create a backup of transaction log file immediately. Once the backup is created, the transaction log is truncated. If you do not take back up of log files, you can also use full or Bulk-Logged Recovery model to simple recovery model.


2. Free Disk Space

Generally, the transaction Log file is saved on the disk drive. So, you can free the disk space which contains Log file by deleting or moving other files on order to create some new space in the drive. The free space on disk will allow users to perform other task and resolve SQL Error Log 9002 The Transaction Log for Database is Full.


3. Move Log File to a Different Disk

If you are not able to free the space on a disk drive, then another option is to transfer the log file into a different disk. Make sure another disk in which you are going to transfer your log file, has enough space.

i. Execute sp_detach_db command to detach the database.

ii. Transfer the transaction log files to another disk.

iii. Now, attach the SQL database by running sp_attach_db command.


4. Enlarge Log File

If the sufficient space is available on the disk then you should increase the size of your log file. Because, the maximum size for a log file is considered as 2 TB per .ldf file.


To enlarge log file, there is an Autogrow option but if it is disabled, then you need to manually increase the log file size.

i. To increase log file size, you need to use the MODIFY FILE clause in ALTER DATABASE statement. Then define the particular SIZE and MAXSIZE.

ii. You can also add the log file to the specific SQL database. For this, use ADD FILE clause in ALTER DATABASE statement.

Then, add an additional .ldf file which allows to increase the log file.

Read More



Unable to add MySQL database in Plesk Customer Panel - Fix it now


This article covers how to fix issues that make it unable to add MySQL database in Plesk customer panel.


To resolve Cannot add MySQL database in Plesk Customer Panel:

1. Log in to Plesk and apply one of the following:

2. Enable Database server selection directive in Service Plans > Default > Permissions > Show more available permissions and press Update & Sync.

3. Switch MySQL default database server from None to localhost:3306 in Service Plans > Default > Hosting Parameters > Default Database Server and press Update & Sync.


Note:  it is also applicable to cases when Amazon RDS extension is installed. 

If it is needed to provide customer with the ability to select Amazon server, enable "database server selection" option.


How do I add a database to my Plesk Panel?

How to Create a New Database or Database User in the Plesk Control Panel

1. Log into your Control Panel.

2. Click on Databases.

3. Click on the Add New Database icon.

4. Next to Database Name enter the name you want to use.

For Type, choose either Microsoft SQL Server or MySQL (DNN uses the Microsoft SQL Server.).

Read More



Checkpoint Process in SQL Server - An Insight into it


This article covers the Checkpoint process in SQL server and the four types of checkpoints available.
Checkpoints are the useful repositories of information and serve best for the recovery of SQL server databases.

Different Types of Checkpoint in #SQL:
1. Automatic Checkpoint
An automatic checkpoint is the most common type that is triggered by a background process. Server Configuration Option “Recovery Interval” is used by the SQL Server Database Engine to determine how often automatic checkpoints are issued on a given database.
2. Indirect Checkpoint
A new type of #checkpoint introduced in SQL Server 2012 is an Indirect checkpoint. Indirect checkpoint also runs in the background, but it meets user-specified target recovery time for a given database.
3. Manual Checkpoint
Manual checkpoint runs like any other Transact-SQL command. It runs to completion by default. This type of checkpoint occurs in the current database only. It is also possible to set the time frame in which you want your checkpoint completed.
4. Internal Checkpoint
The fourth type is Internal checkpoint that cannot be controlled by user.

Read More



Plesk Panel Database issues


This article covers the different #Plesk database errors. The main reason for database issues in Plesk is the misconfiguration of the PSA database.
Plesk employs the native functionality of database management tools for checking and repairing databases.
For example, for #MySQL databases it uses the mysqlcheck utility.

To check and repair a #database:
1. Go to Websites & Domains > Databases > Check and Repair in a database tools pane.
2. If problems are found, click the link See Details and Resolve.
3. The list of tables and corresponding problems will open.
For MySQL databases, you can choose the tables that you would like to repair.
For Microsoft SQL databases, you can repair an entire database only.
Click Repair Selected (for MySQL) or Repair (for Microsoft SQL).

Read More



Perfmon counters for Disk Usage


This article will guide you on use performance counters (#Perfmon) to identify SQL server disk bottlenecks. 

The performance impact is negligible in updating. Microsoft's intent is that you always write to the performance counters. It's the monitoring of (or capturing of) those performance counters that will cause a degradation of performance. So, only when you use something like perfmon to capture the data.

Reliability #Monitor shows you your system stability history at a glance and lets you see details on a day-by-day basis about events that impact reliability. Reliability Monitor provides a quick view of how stability the system has been.

1. The Performance Monitor is primarily for viewing real time #statistics. 

2. By default only one counter is selected; the %Processor Time counter. However you can add additional counters by clicking on the green plus sign. 

3. This will allow you to monitor any counters you wish in real time.

4. Difference Between Performance Monitor and #Resource Monitor is that a performance monitor is a program that assesses and reports information about various computer resources and devices. 

5. While Resource Monitor is a tool by which you can monitor the usage of your CPU.

Read More



Perfmon Counters for memory usage


This article will guide you on how to use Perfmon Counters for memory usage. You will also learn some commonly used performance counters which can be used to identify #SQL server memory pressure.

To detect a memory leak using #Performance #Monitor, monitor these counters: The Memory/Available Bytes counter lets you view the total number of bytes of available memory. This value normally fluctuates, but if you have an application with the memory leak, it will decrease over time.

A system performance report is a part of Performance Monitor that details the status of local hardware resources, system response times, and processes on the local computer. You can use this information to identify possible causes of performance issues.

SQL performance tuning consists of making queries of a relation database run as fast as possible. 

To Check Detailed #Memory #Usage with Performance Monitor:

1. To open up Performance Monitor type: perfmon into the Run window (Windows Key + R). 

2. In the window that comes up, click the Performance Monitor under Monitoring Tools in the left pane. 

Read More



Install SQL Server 2019 on Linux


This article will guide you the process to install #MSSQL Server 2019 on #CentOS 7 and Ubuntu 16.04.

SQL Server 2019 #Developer is a full-featured free edition, licensed for use as a development and test database in a non-production environment.

SQL Server 2019 allows us to integrate data from structured and unstructured data sources. 

We can now process diverse big data and relational data sources using Transact-SQL from SQL Server using PolyBase. 

We can see below PolyBase support external databases.

SQL Server Express can be used in production (beware of the limitations, like the 10GB cap), but according to this link Express is available for Linux. SQL Server Express is available to use in Production.

Starting with SQL Server 2017, SQL Server runs on Linux. It's the same SQL Server database engine, with many similar features and services regardless of your operating system. It's the same SQL Server database engine, with many similar features and services regardless of your operating system.

To run a SQL script in #Linux terminal:

1. Open Terminal and type mysql -u to Open the MySQL command line.

2. Type the path of your #mysql bin directory and press Enter.

3. Paste your #SQL file inside the bin folder of mysql server.

4. Create a #database in MySQL.

5. Use that particular database where you want to import the SQL file.

Read More



MSSQL replication setup


This article will guide you on how to setup #MSSQL replication and fix related errors. The MSSQL replication is a bit long procedure to configure replication. 

Through embedded SQL database replication technology, #SQL Server supports three types of #replication: snapshot, transactional, and merge replication.

#Snapshot replication sends the entire data set to the subscriber. 

Transactional replication only sends modifications to the data. 

Merge replication items are modified at both the publisher and subscribers. 

Heterogeneous replication allows access to other database products.

To enable replication in SQL Server:

Using SQL Server Management Studio (#SSMS)

1. On the Publication Databases page of the Publisher Properties - <Publisher> dialog box, select the Transactional and/or Merge check box for each database you want to replicate. 

2. Select Transactional to enable the database for snapshot replication.

3. Click OK.

Read More



Modify MSSQL port


This article will guide you on the right steps to change the #MSSQL port using #SQL Server Configuration Manager. 

You can check TCP/IP connectivity to SQL Server by using telnet. For example, at the command prompt, type telnet 192.168. 0.0 1433 where 192.168. 0.0 is the address of the #computer that is running SQL Server and 1433 is the port it is listening on.

To specify a port in SQL Server Management Studio (#SSMS)?

1. You'll need the SQL Server Configuration Manager. 

2. Go to Sql Native Client Configuration, Select Client Protocols.

3. Right Click on #TCP / #IP and set your default port there.

Read More



Plesk MSSQL remote connection


This article will guide you on how to enable and resolve #MSSQL related #errors. MSSQL remote connection is disabled in #Plesk servers by default.

To enable remote connections to MS SQL server:

1. Connect to the server via RDP.

2. Press the Start button, go to Microsoft SQL Server XXXX (where XXXX is the MSSQL version) and click the SQL Server XXX Configuration Manager.

3. Open the SQL Server Configuration Manager (Local) > #SQL Server Network Configuration menu and click the Protocols for MSSQLSERVERXXXX (where XXXX is the MSSQL version).

4. Make sure that the TCP/IP protocol has the Enabled status

5. Double-click the TCP/IP protocol, go to the IP Addresses tab and scroll down to the IPAll section.

6. Specify 1433 in the TCP Port field (or another port if 1433 is used by another MS SQL Server) and press the OK button:

Note: the specified port, e.g, 1433, must be opened in the firewall.

Read More



SQL server error 1326 Steps to fix it


This article will guide you on methods to resolve SQL server error 1326 which occurs due to the IIS Service not having any rights to use the named pipe.

If the SQL server resides on a separate server from IIS, then the IUSR_machinename account needs to be validated on the Windows NT server that SQL resides on.

#SQL #SERVER – Fix : Error : 1326 Cannot connect to #Database Server Error: 40 – Could not open a connection to SQL Server.

Now if SQL Server can be connected perfectly from #local system, but cannot be connected from a remote system, in that case firewall on the server where SQL Server is installed can be issued.

Follow instructions below to fix the issue:

1. Go to control panel >> #Firewall Settings >> Add SQL Server’s Port to Exception List.

2. Now try to connect to SQL Server again. It will allow you to connect to the server successfully.

Read More



Microsoft SQL server error 18470 How to fix it


This article will guide you on the different factors that causes SQL server error: 18470 and also how to fix this #error.

In SQL Server Configuration Manager, in the left pane, click SQL Server Services. In the results pane, right-click SQL Server (#MSSQLServer) or a named instance, and then click Start, Stop, Pause, Resume, or Restart.

User gets the #Microsoft SQL Server Error: 18470. This may happen if the SA (System Administrator) user account is disabled in #SQL Server. It can be verified by trying to log in to SQL Server Management Studio (#SSMS) using the SA account. In the Login Properties screen, select Status on the left side.

To Microsoft SQL Server Error 18456:

1. Log In with Remote Desktop.

2. Run Microsoft SQL Server Management.

3. Checking the Server Authentication Mode.

4. Restart the SQL Service.

5. Checking SQL User Permissions.

6. Mapping the User to the #Database.

Read More



Restrict anonymous login and ban IP address of attacker Windows


This article will guide you on the steps to Restrict anonymous login and ban #IP address of attacker by using Local Group Policy Editor in #Windows which allows us to prevent anonymous login and #IPBan helps to ban IP of #attacker. 

Read More



SQL error Msg 4341


This guide will help you to fix SQL error Msg 4341 which can occurs during a database recovering process to a point in time. 

Read More



Solve SQL Server event id 833


Best method to fix SQL server error 833 and optimizing database performance.

Read More




For Linux Tutorials

We create Linux HowTos and Tutorials for Sys Admins. Visit us on LinuxAPT.com

Also for Tech related tips, Visit forum.outsourcepath.com or General Technical tips on www.outsourcepath.com






Focus on your business, not your servers.

Click Here to Learn More