Explore information related to ms sql

Unable to add MS SQL database in Plesk - Fix it now

This article covers how to fix the error, Unable to add MS SQL database in Plesk.

Basically, the number of MS SQL databases is limited for the webspace, subscriptions, or reseller's plan.


In Web Admin Edition:

1. Log in to Plesk.

2. Go to Tools & Settings > License Management and check if Microsoft SQL Server support enabled or not:

a. If no, then it is required to purchase the MSSQL support first for the subscription.

MSSQL support is included in the Power Pack and Developer Pack.

b. If yes, then proceed to step 3.

3. Run the command below to get the current limit of MSSQL databases for the required webspace:

C:\> plesk bin subscription_settings --info example.com | findstr max_mssql_db

max_mssql_db 30 MS SQL databases

4. Increase the number of MSSQL databases for the required webspace (use the "-1" to set to the Unlimited value):

C:\> plesk bin subscription_settings -u example.com -max_mssql_db 100

plesk bin subscription_settings -u example.com -max_mssql_db -1


In Web Pro and Web Host Editions:

1. Log in to Plesk.

2. Go to Subscriptions > example.com > Account > Resources.

3. Find the MS SQL databases number.

a. If it reached its limit, increase it of the following ways:

Go to Subscriptions > example.com > Customize > Resources page and increase the MS SQL databases limit (changes will affect only this subscription).

Go to Subscriptions > example.com > Service Plan: Default > Resources page and increase the MS SQL databases limit (changes will affect all subscriptions assigned to this service plan).

b. If it is not reached the limit, then this limit is set on the reseller's level as also. Follow to the next step.

4. Go to Subscriptions > example.com > Subscriber: John Doe > Provider: Jane Doe.

5. Click the Change Plan button to increase the MS SQL databases number for all resellers assigned to this service plan.

Click the Customize button to increase the MS SQL databases number only for this reseller.

6. Find the MS SQL databases number and increase it to the required value.

Read More


Delete Data in SQL using DELETE statement - How to use it

This article covers how to Delete Data in SQL using the DELETE statement. 

The SQL DELETE Query is used to delete the existing records from a table.

You can use the WHERE clause with a DELETE query to delete the selected rows, otherwise all the records would be deleted.


In Structured Query Language, more commonly known as SQL, the DELETE statement is one of the most powerful operations available to users. 

DELETE operations irreversibly delete one or more rows of data from a database table. 

Being such a fundamental aspect of data management, it's important for SQL users to understand how the DELETE statement works.


The basic syntax of the DELETE query with the WHERE clause is as follows:

DELETE FROM table_name
WHERE [condition];

You can combine N number of conditions using AND or OR operators.


Note: Be careful when deleting records in a table! Notice the WHERE clause in the DELETE statement. 

The WHERE clause specifies which record(s) should be deleted. If you omit the WHERE clause, all records in the table will be deleted!


To Delete All Records:

It is possible to delete all rows in a table without deleting the table. This means that the table structure, attributes, and indexes will be intact:

DELETE FROM table_name;


DROP is used to delete a whole database or just a table. The DROP statement destroys the objects like an existing database, table, index, or view. A DROP statement in SQL removes a component from a relational database management system (RDBMS).

Read More


SQL Server Memory Allocation

This article covers SQL server memory allocation best practices to follow while allocating memory.
By default, SQL Server can change its memory requirements dynamically based on available system resources.
SQL Server is designed to use all the memory on the server by default.
The reason for this is that #SQL Server cache the data in the database in #RAM so that it can access the data faster than it could if it needed to read the data from the disk every time a user needed it.
Changing SQL Server's Max Server memory is an online option – you don't need to restart SQL Server.
Though when you do make the change, you can and likely will cause data or procs to leave their caches so things could be a slight bit slower for a short while after you run it.
SQL Server will always give you better performance because the query is executed on the server.
Access on the back-end won't help because your client application will need to pull all the data from the tables, and then perform the join locally.
SQL Server has better indexing options.
'Max server memory' ensures that SQL Server buffer pool will not use more memory than specified in 'max server memory'.
So, SQL Server can use less memory than the value of 'max server memory' and other services can use the remaining memory.

You can monitor memory use at the database level as follows:
1. Launch SQL Server Management Studio and connect to a server.
2. In Object Explorer, right-click the database you want reports on.
3. In the context menu select, Reports -> Standard Reports -> Memory Usage By Memory Optimized Objects.

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


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


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


Configure Reporting Services in SQL Server

The article will guide you on the steps to follow to configure #reporting services after renaming the #SQL server. Also , you will learn how to rename the SQL server instance. 

To Configure #Report Server After Renaming SQL Server #Instance:

1. Go to #Database Setup page. 

2. Enter SQL Server name in Server Name and then click Connect. 

3. If Reporting Services is configured using the server name, you must update the database connection information whenever the server name is changed.

To change the service account for SQL Server Reporting Services:

i. Open Reporting Services Configuration Manager, and then connect to the instance of SQL Server Reporting Services.

ii. Click #Microsoft service Identity on the left pane.

iii. Change the account and the password in the Account text box and the Password text box, and then click Apply.

Read More


Steps to create SQL server alias

Steps for Deleting an alias using SQL Server Configuration Manager ?
#SQL aliases are used to give a table, or a column in a table, a temporary name. Aliases are often used to make column names more readable. An alias only exists for the duration of the query.
To find my SQL Server #alias name:
Expand SQL Native client #configuration, and you can find a subfolder Alias. By default, we do not have any alias defined for the SQL Server #instance. In the screenshot, we can see it does not see any items for the Alias. Right-click on Aliases and click on New Alias.
1. Take SQL Server Configuration Manager and go to SQL Server Native #Client Configuration, then click Aliases.
2. We can right-click the alias that we want to delete, and then click Delete.
3. A warning will pop up, we can click on Yes to remove the alias. This removes the SQL Server alias.

Read More


SQL Server and create a database on Ubuntu How to install

This article will guide you on how to #install MS SQL on #Ubuntu Server 18.04. 

To Install #Microsoft SQL Server 2017:

1. Visit Microsoft's official SQL Server 2017 download page.

2. Select the edition you want to #download. 

3. Click Download now below your selected edition. 

4. The wizard will prompt you to select an installation type. 

5. On the next page, select a directory for the installation folder.

To connect to the SQL Server using #SSMS:

i. From the Connect menu under the Object Explorer, choose the #Database Engine.

ii. Then, enter the information for the Server name (localhost), Authentication (SQL Server Authentication), and password for the sa user.

iii. Click the Connect button to connect to the SQL Server.

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


Repair corrupt sql bak file

This guide will help to repair corrupt sql .bak file when it comes to cases where you need to perform a data disaster prevention by means of database backup.

Read More


SQL error Msg 3266

This article will help you to solve SQL error Msg 3266 which occurs when database backups job fails when the filemark in the backup device cannot be read. 

Read More


Recovering a database from suspect mode in SQL

This article will guide you through the process of repairing  a database which is in Suspect mode in SQL by performing consistency check on database in emergency mode and executing ALLOW DATA LOSS in single user mode.

Read More


Doing page level restore in SQL server

Best way to perform page level restore in SQL server.

Read More


Solve SQL Server event id 833

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

Read More