Explore information related to sql server

Manage Transaction Log File during Data Load - Do it Now

This article covers how to manage transaction log files in SQL Server for our customers. A transaction log is a file – integral part of every SQL Server database. It contains log records produced during the logging process in a SQL Server database.

The transaction log is the most important component of a SQL Server database when it comes to the disaster recovery – however, it must be uncorrupted.

The only way to truncate the log, so the space can be reused, is to perform a SQL transaction log backup. Therefore the most common reason for a transaction log file to have grown extremely large is because the database is in the FULL recovery model and LOG backups haven't been taken for a long time.


How do I stop a transaction log from filling up?

1. To keep the log from filling up again, schedule log backups frequently. 

2. When the recovery mode for a database is set to Full, then a transaction log backup job must be created in addition to backing up the database itself.


To fix a transaction log for a database is full:

1. Backing up the log.

2. Freeing disk space so that the log can automatically grow.

3. Moving the log file to a disk drive with sufficient space.

4. Increasing the size of a log file.

5. Adding a log file on a different disk.

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


SQL Error 17051 – Server Evaluation Edition to Enterprise Edition

This article covers method to resolve SQL Error 17051.

This SQL error  sometimes happens when the SQL Server Evaluation period has expired.

To fix Microsoft SQL Server Management Studio error:
1. Now as per the error message you open the Event Viewer and see that the Event with ID 17051, which shows SQL Server Evaluation period has expired under Details section.
2. Now, you recall that the Instance that you had installed was under Evaluation of 180 days, because you didn’t applied any Product Key. So, now how can you make it live again? All you need is a Product key of SQL Server and some clicks.
3. Open the SQL Server Installation Center and click on Maintenance link, and then click on Edition Upgrade.
4. Now on the Upgrade window Click Next and you will reach the Product Key page, apply the Key and click Next.
5. On the Select Instance page, select the SQL Instance that you want to fix and Click next. It will take some time and finally you will see a final window and click Upgrade.
6. Finally you will see the successful window, click on Close button.

Also, you can use following command line installation option to skip this specific rule to allow the upgrade process to complete successfully:
a) Open Command Prompt (CMD)
b) Go to the folder where SQL Server Setup, setup.exe file is located (like C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\)
c) Apply following command:

setup.exe /q /ACTION=editionupgrade /InstanceName=MSSQLSERVER /PID=<appropriatePid> /SkipRules= Engine_SqlEngineHealthCheck

The <appropriatePid> should be the 25 digit Key.
The above command line runs SQL Server setup in silent mode.
Now Restart the SQL Server Service for this Instance, and you will see it running fine.
Finally, go back to SSMS and now you can connect to the SQL Instance.

Read More


Microsoft SQL Server Error 916 - Fix it now

This article covers method to resolve Microsoft SQL Server Error 916 for our customers.

The main problem is due to bugs present in SQL Server Management Studio that prevents the user to connect to the database and refuses to display the database list.

How to solve Microsoft SQL server error 916:
If you receive the following error while using Microsoft SQL Server Management Studio 2008:
The server principal "username" is not able to access the database "dbname" under the current security context. (Microsoft SQL Server, Error: 916).

Causes of SQL Server Error 916:
1. The user is not permitted to view the data of selected column within the database.
2. The database is currently not available.
3. There are multiple columns such as Size, Space available, Data Space Used, Default file group, Index Space Used, Mail host, Primary file path and user has added at least one of them to the list of Object Explorer Details.
4. If the Auto Close option for the database is enabled, then Collation column cannot be retrieved by SQL Server Management Studio (SSMS).
5. For a database, Collation column contains NULL.

In order to view the granted permissions for the guest-user, the following command is helpful if run by a member of a Sysadmin fixed server.
The query is as follows:

USE msdb;
 SELECT prins.name AS grantee_name, perms.*
 FROM sys.database_permissions AS perms
 JOIN sys.database_principals AS prins
 ON perms.grantee_principal_id = prins.principal_id
 WHERE prins.name = ‘guest’ AND perms.permission_name = ‘CONNECT’;
 GO

On running the above command, a table is presented to the user containing all the attributes of guest user.
However, an empty result shows that guest user is disabled in the database and again the SQL Server error 916 will be displayed.
To overcome the error you may perform the following available solutions.

To fix this SQL server error 916:
1. In Object Explorer, click databases.
2. Display "Object Explorer Details" (F7) or "View –> Object Explorer Details".
3. Right-click the column headers and deselect "collation".
4. Refresh the databases.

Read More


Attributes do not match - Fix this SQL Server Installation Error

This article covers how to resolve the error, SQL Attributes do not match. Basically, the error, Attributes do not match occurs during SQL Server installation or during SQL Server patching activity.
Once you get this issue, you can check all drives available on your database server whether they are compressed or not. If any drive is compressed and SQL Server is using that drive during installation then that might be the reason for getting issue Attributes do not match.
You need to uncompress all such drives and then start the installation.

To uncompress the drive we need to launch property window of that drive:
1. We just need to right click on the identified drive and choose Properties to see the status of compression.
2. You can see compress this drive to save disk space option is ticked.
3. Uncheck this option and click on OK button to apply the change.
4. Once you validated all drives that none of the drives are compressed then you can start SQL Server installation and this time SQL Server installation will be successful.

When installing SQL server and running into an error "Attributes do not match.
Present attributes (Directory, Compressed) , included attributes (0), excluded attributes (Compressed, Encrypted)".
This is because you are trying to install SQL into a folder that is compressed which is not supported.
To fix this;
1. Navigate to C:\Program Files\Microsoft SQL server folder
2. Right click on properties on SQL Server folder.  
3. Under advanced option in general tab, look for compress contents to save disk space, uncheck it.
4. Also, uncheck "encrypt contents to secure data"
5. Re-run the SQL install

Read More


SQL Error 50000 - Best method to fix

This article covers method to fix SQL Error 50000.

This SQL error happens in the process of installing SQL Server Management Studio on one of the client machines.
If you receive SQL Server 50000 error on a SQL Agent Job, you need to Quit the job reporting failure.

To fix this SQL error, you can try the following queries:
1. Enable the SQL Broker on the Site database:

USE master; 
GO 
ALTER DATABASE CM_PR1 SET ENABLE_BROKER 
GO

2. SET the Site Database as trustworthy:
USE master;

GO 
ALTER DATABASE CM_PR1 SET TRUSTWORTHY ON 
GO

3. SET the Database to honor the HONOR_BROKER_PRIORITY:

USE master; 
GO 
ALTER DATABASE CM_PR1 SET HONOR_BROKER_PRIORITY ON; 
GO

Read More


SQL Server Error 5009 – Different scenarios and fixes

This article covers how to fix SQL Server Error 5009 error which occurs while adding or removing a database file or extending the database file size.
 
To fix Microsoft SQL Server Error 5009 While Adding Database File:
1. Set the Operating system permission on the mentioned .ldf file to full permission for your login account and SQL Server service account.
2. Change the location to the path where you have enough permission to create or add database files.

Read More


SQL error 300 - Fix it Now

This article covers tips to resolve SQL error 300. The reason of the error is related with user permission on VIEW SERVER STATE. You can upgrade SQL Server Management studio with the same version like SQL Instance or higher. 


Also, To mitigate this error, give the following GRANT and the error message will disappear:

USE master
GO
GRANT VIEW SERVER STATE TO "LoginName"

Read More


Features Of SQL Server 2019 - More Insight

This article covers the main features of SQL Server 2019. SQL Server 2019 features Data virtualization and SQL Server 2019 Big Data Clusters.

With Read, write, and process big data from Transact-SQL or Spark. Easily combine and analyze high-value relational data with high-volume big data. Query external data sources. Store big data in HDFS managed by SQL Server.


The Main Features of SQL Server 2019 includes:

1. Intelligent Query Processing Enhancements.

2. Accelerated Database Recovery (ADR).

3. AlwaysEncrypted with secure enclaves.

4. Memory-optimized Tempdb metadata.

5. Query Store custom capture policies.

6. Verbose truncation warnings.

7. Resumable index build.

8. Data virtualization with Polybase.


How do I start SQL Server?

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.


To uninstall SQL Server from Windows 10, Windows Server 2016, Windows Server 2019, and greater, follow these steps:

1. To begin the removal process navigate to Settings from the Start menu and then choose Apps.

2. Search for sql in the search box.

3. Select Microsoft SQL Server (Version) (Bit).

4. Select Uninstall.

Read More


MySQL crash – Causes Recovery and Prevention methods

This article covers methods to fix and prevent MySQL downtime. Basically, many issues such as resource limits, #database table errors, file system errors, and so on, can lead to a MySQL crash.


To fix MySQL errors in cPanel?

You can also restart the MySQL service from WHM.

1. Login to WHM.

2. Navigate to Restart Services.

3. Now you can restart the MySQL service by clicking the icon “SQL Server(MySQL)”.


To use mysqlcheck, follow these steps:

1. As the root user, type the following command: cd /var/lib/mysql.

2. Replace the database with the name of the database that you want to check.

3. Mysqlcheck checks the specified database and tables.


How do I know if MySQL is running?

We check the status with the service mysql status command. We use the mysqladmin tool to check if MySQL server is running. 

The -u option specifies the user which pings the server. 

The -p option is a password for the user.


What does repair table do MySQL?

REPAIR TABLE repairs a possibly corrupted table, for certain storage engines only. 

This statement requires SELECT and INSERT privileges for the table. Although normally you should never have to run REPAIR TABLE , if disaster strikes, this statement is very likely to get back all your data from a MyISAM table.


What causes MySQL #tables to crash?

The major cause of the database corruption is the lack of free disk space on the server.

Other possible causes of MySQL table crashes include operating system problems, power failures, hardware issues, unexpected MySQL server termination, data corruption due to external programs, and so on.


To access your #MySQL database in Linux, please follow these steps:

1. Log into your Linux web server via Secure Shell.

2. Open the MySQL client program on the server in the /usr/bin directory.

3. Type in the following syntax to access your database: $ mysql -h {hostname} -u username -p {databasename} Password: {your password}

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


Difference between BACPAC and DACPAC - More insight

This article covers more information about BACPAC and DACPAC and the difference between BACPAC and DACPAC.
A BACPAC file is a ZIP file with an extension of BACPAC containing the metadata and data from the #database. A BACPAC file can be stored in Azure Blob storage or in local storage in an on-premises location and later imported back into Azure SQL Database, Azure SQL Managed Instance, or a SQL Server instance.
DACPAC = Data Tier AppliCation Package. DACPAC is a single file which contains database model i.e. all files represent database objects. It's a binary representation of database project compatible with SSDT. The name comes from an extension of these files.
Once you extract the contents of the #DACPAC file, you'll see there are four different XML files within it.
These XML files do not contain any data from the database.
The database is scripted out only with the model information.

To import from a #BACPAC file into a new single database using the Azure portal:
1. Open the appropriate server page and then, on the toolbar, select Import database.
2. Select the storage account and the container for the BACPAC file and then select the BACPAC file from which to import.

Data tier controls the servers where the information is stored;
1. It runs a relational database management system on a database server or a mainframe and contains the computer data storage logic.
2. The data tier keeps data independent from application servers or processing logic and improves scalability and performance.

To import a .BAK file into #SQL Server:
1. Open #SSMS and click on Connect.
2. First let us go with Bak File importing.
3. Check the Device Button and Click on it.
4. Click on Add Button, choose the Appropriate bak file and then click on Ok.

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


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 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


Reporting services configuration manager

This article will guide you on how to setup reporting services configuration manager. Report Manager is Web based interface that can be used to perform different tasks such as. Administer the Report Server,View the Reports and Manager the Report, and so on. You need to have the URL to access the Report Server by using Report Manager interface.

SQL Server Reporting Services (#SSRS) is a reporting #software that allows you to produce formatted reports with tables in the form of data, #graph, images, and charts. These reports are hosted on a server that can be executed any time using parameters defined by the users.

Report server items are always stored in libraries or in a folder within a library. 

When you access the SharePoint site, you see the Browse page and the Library Tools tab.

In #Reporting Services, URLs are used to access the Report Server Web service and the web portal. A test link of the URL appears on page when you define the URL so that you can immediately confirm that the settings you specified result in a valid connection.

To connect to Reporting Services Configuration Manager:

1. Click Start, then click #Programs, then click #Microsoft #SQL Server, then click Configuration Tools, and then click Report Server Configuration Manager. 

2. The Report Server Installation Instance Selection dialog box appears so that you can select the report server instance you want to configure.

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


MySQL is not running

This article will guide you on methods to resolve MySQL #error 'MySQL is not running'. Basically, this MySQL error occurs due to many reasons that include stopping MySQL improperly, tables crashing and so on. 

Both MySQL and #Microsoft SQL Server (MSSQL) are widely used enterprise database systems. MySQL is an open-source relational #database management system (RDBMS), while MSSQL Server is a Microsoft-developed RDBMS. 

Enterprises can choose between multiple #MSSQL Server editions to suit their individual needs and budgets.

Why #MySQL is not opening?

1. You can also check the MySQL service is running in background or not. 

2. To do that open Task manager ( Press CTRL + SHIFT + ESC simultaneously ) and look for mysqld service in background process section. 

3. If it isn't listed there then the service is stopped or disabled.

Read More


Configure and Use Microsoft SQL Server Management Studio

This article will guide you on how to setup SQL server management studio. SQL Server Management Studio is a free #Windows #application to configure, manage, and administer Microsoft SQL Server (#MSSQL). 

SSMS is available only as a 32-bit application for Windows.

To get SQL Server Management Studio:

1. Go To Start Menu>Programs>Microsoft SQL Server Tools 18> Microsoft #SSMS 18. 

2. Below 'Connect to Server' screen will appear. 

3. Server Name defaults to the name selected while installing MS SQL server. 

4. Server type: This is an option to select one out of four available MS SQL services option.

To Enable remote connections to your SQL Server:

i. Open #SQL Server Management Studio.

ii. Right-click your server's name and select Properties.

iii. Tick the checkbox Allow remote connections to this server.

iv. Select OK.

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


Wildcards in SQL Server

This article will guide to use #Wildcards in #SQL server. Also you will learn how to use and escape wildcards SQL-based databases. 

To use a wildcard character within a pattern: Open your #query in Design view. In the Criteria row of the field that you want to use, type the #operator Like in front of your criteria. Replace one or more characters in the criteria with a wildcard character.

i. The wildcard is an advanced search technique that can be used to maximize your search results in library databases. 

ii. Wildcards are used in search terms to represent one or more other characters. 

iii. The two most commonly used wildcards are: An asterisk (*) may be used to specify any number of #characters.

Read More


SQL error 825 How to fix it

This article will guide you on methods to resolve SQL error 825 which indicates a major disk problem and not a SQL server problem. 

The connection to #SQL server cannot be established or is no longer usable. There can be various causes of this #error. The most common causes are that Microsoft Dynamics NAV Server has stopped or the connection to SQL #Server is not configured correctly.

To find SQL errors:

i. In SQL Server Management Studio, select Object Explorer.

ii. In Object Explorer, connect to an instance of SQL Server, and then expand that instance.

iii. Find and expand the Management section (assuming you have permissions to see it).

iv. Right-click SQL Server Logs, select View, and then choose SQL Server Log.


Every SQL Server #database has a transaction log that records all transactions and the database modifications made by each transaction. The transaction log is a critical component of the database. If there is a system failure, you will need that log to bring your database back to a consistent state.

To get SQL query history in SQL Server:

1. In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance.

2. Expand SQL Server Agent, and then expand Jobs.

3. Right-click a job, and then click View History.

4. In the Log File Viewer, view the job history.

5. To update the job history, click Refresh.

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


Restore a database in Alwayson Availability Group

This article will guide you on steps to restore a #database in alwayson availability group.

If you receive an #error that the database is in use, try to set the user to single user mode: USE master; GO ALTER DATABASE Database_name SET SINGLE_USER WITH ROLLBACK IMMEDIATE; Then try the restore with #recovery command again. Also, make sure you are on the latest service pack or cumulative update.

Creating a #SQL #Server AlwaysOn Availability Group.

Open SQL Server Management Studio and connect to the SQL Server instance. Expand the AlwaysOn High Availability folder in the Object Explorer. Right-click on the Availability Groups folder and select the New Availability Group Wizard.

To Restore a Database in a SQL Server AlwaysOn Availability Group:

1. Make the secondary server from which the backups were taken the primary server.

2. Remove the database to be restored from the AlwaysOn Availability Group.

3. Restore the database.

4. Add the database back into the Always Availability Group.

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


Database version or build from backup file

This article will guide you on how to determine the database #version or build from a #backup file.
To know what #SQL version a #database is:
The first is by using either Enterprise Manager or SQL Server Management Studio and right clicking on the instance name and selecting Properties. In the general section you will see information such as on the following screenshots. The "Product version" or "Version" gives you a number of the version that is installed.
In order to find the SQL Server version from a bak file:
1. Here is the output returned by the RESTORE HEADERONLY statement. Here you will see a DatabaseVersion column that contains the value.
2. That's how you find out from which version of SQL Server a given backup file came.

Read More


Improve SQL Server Bulk Data Import Performance

This article will guide you improve #bulk #data #import #performance. The BULK INSERT command is much faster than bcp or the data pump to perform text file import operations, however, the BULK INSERT statement cannot bulk copy data from #SQL Server to a data file. Use the bcp utility instead of DTS when you need to export data from the SQL Server table into a text file.
To Speed up SQL Bulk Insert with #transactions:
1. Declare the variables that store the number of desired items ( @items ), the size of the chunks( @chunk_size ) and the counter of the number of executed inserts( @counter )
2. Open the first transaction and initialize the while loop.

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


Perfmon Counters for CPU usage

This article will guide you on how to use #Perfmon Counters for CPU #Usage and #Optimization.
Monitoring #CPU #Performance #Counters:
1. System, #Counter: Processor Queue Length. This Performance Monitor counter displays the number of threads waiting to be executed in the queue, which all the processors on your system share.
2. Processor, Counter: % Processor Time.
3. Processor, Counter: Interrupts/sec and Performance Object; Processor, Counter: % DPC Time.

Read More


Orphaned users in SQL Server

This article will help you to identify #Orphaned #Windows #Logins and Groups in #SQL Server.
To Resolve an Orphaned User:
To map an orphaned user to a login which already exists in master, execute the ALTER USER #statement in the user database, specifying the login name.
ALTER USER <user_name> WITH Login = <login_name>; When you recreate a missing login, the user can access the database using the password provided.
To fix orphaned users for all databases in SQL Server:
1. Login with same name as user exists – generate ALTER LOGIN to map the user to the login.
2. No login with same name exists – generate DROP USER to delete the orphan user.
3. Orphan user is [dbo] – change the database owner to SA (or whatever SA was renamed to).

Read More


Auto shrink feature in SQL server

This article will guide you on how to enable and disable AutoShrink #database property. Basically, it is not recommended to enable the AutoShrink database property as it can cause many issues in the #SQL Server.
Auto Shrink is database property that allow SQL Server to automatically shrink database files if its value set to ON/True. Shrinking a database is not a good practice because it is very expensive operation in terms of I/O, CPU usage, locking and #transaction log generation.
Users can enable and disable database auto shrink option using SSMS and T-SQL both ways.
To turn on auto shrink in SQL Server:
1. Activating the database auto shrink by using #SSMS:
2. Enable database auto shrink using T-SQL:
3. Database >> #Reports >> Standard Reports >> Disk Usage.
4. Check free space for the database files:
5. Shrink database file:

Read More


Virtual Log Files in SQL Server

This article will guide you on how to find the total number of #VLFs. The DMF sys.dm_db_log_info specifically looks at virtual log files or VLFs for which it needs a database ID for input.

To find it, check the number of virtual log files (VLFs) in each #database and alerts when there's 1,000 or more.

Read More


SQL server Error 1053

This article will guide you on different methods of fixing error #1053 SQL server which occurs when attempting to pause or stop the SQL Server service in the #Windows Services Console. 

The most common cause of this error is when one of the files needed by sql server was not on a shared resource, and Sql Server, once failed to the other node, couldn't access it.

The #SQL #Server Agent error log may include a path or a file name that is not correct.

In this case, verify that the path and file name for SQLAgent.out is valid:

1. In SQL Server Enterprise Manager, expand the Management folder.

2. Right-click SQL Server Agent, and then click Properties.

3. Under Error Log, make sure that the path that is specified next to File Name is valid.

4. Make sure that the file name is SQLAGENT.out.

Read More


Instant File Initialization in SQL server

This article will guide you on how to enable Instant File Initialization (#IFI) in #SQL Server. 

Disk space reservation without initialization is called Instant File Initialization. 

To enable #database instant file initialization:

1. First, go to Start Menu and run secpol.msc to bring up Local #Security #Policy.

2. Expand the Local Policies Folder.

3. Click on User Rights Assignment.

4. Go to the Perform Volume Maintenance Tasks option and double click it.

5. Add your SQL Server Service account, and click OK.

6. Restart your SQL Server services (MUST DO).


Read More


How to create bacpac file from SQL server

This article will guide you on how to export an existing #database into a #BACPAC file is through #SSMS. A bacpac is a dacpac + data, while a dacpac only contains the schema of the database.

To create a Bacpac file:

a. To #export a database using the Azure portal, open the page for your database and click Export on the toolbar.

b. Specify the BACPAC filename, select an existing Azure storage account and container for the export, and then provide the appropriate credentials for access to the source database.

c. Click OK.

To import from a BACPAC file into a new single database using the Azure portal:

1. Open the appropriate server page.

2. On the toolbar, select Import database. 

3. Select the storage account and the container for the BACPAC file and then select the BACPAC file from which to import.

Read More


Setting up client access over private IP address to MySQL on Compute Engine

This article will guide you on setting up client access over private IP address to #MySQL on #Compute #Engine helps advanced usage of parameters and specific performance needs.

To allow IP to connect to MySQL:

1. Edit MySQL Config File. 1.1 Access mysqld.cnf File. 

2. Set up Firewall to Allow Remote MySQL Connection. While editing the configuration file, you probably observed that the default MySQL port is 3306. 

3. Connect to Remote MySQL #Server. Your remote server is now ready to accept connections.

Read More


How to modify MSSQL Database Autogrowth Configuration

This article will guide you on how #MSSQL Database Autogrowth Configuration works. Therefore do not rely on the default #SQL Server Data and Log file Autogrowth value and must always set it to more realistic values depending upon the usage of the database.

To see data file growth in SQL #Server:

1. Connect to a SQL instance and right-click on a database for which we want to get details of Auto Growth and Shrink Events. 

2. It opens the disk usage report of the specified #database. 

3. In this #disk usage report, we get the details of the data file and log file space usage.

To Change default database location via SQL Server Management Studio:

i. Right Click on Server and Select "Properties".

ii. In the "Server Properties" dialog box, navigate to "Database Settings" tab and data/log files location under "Database default locations" group. 

iii. Click on "OK" to apply changes.

Read More


Steps to install MySQL in Docker Container

This article will guide you on the steps to install and configure #MySQL in #Docker #container. MySQL is a well-known open-source relational #database management system and one of the most popular web server solutions. It stores and structures data in a meaningful manner, ensuring easy accessibility. Setting up a database in Docker is simply building a container based on a MySQL #image. 

To Set Up & Configure a MySQL Docker Container:

1. Running a MySQL Docker Container.

2. Installing a MySQL Docker Container.

i. Pull the MySQL Docker Image.

ii. Deploy the MySQL Container.

iii. Connect to the MySQL Docker Container.

3. Configure MySQL Container. Manage #Data Storage.

4. Start, Stop, and Restart MySQL Container.

5. Delete MySQL Container.

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


Deploying Kohana PHP application on Debian

This article will guide you on how to deploy Kohana on #Debian. Kohana offers powerful event handling, multiple session drivers, simple database abstraction using #SQL helpers, and libraries that transparently handle external APIs. Its generous BSD license lets developers use and modify the framework to build commercial applications.

The #AppDynamics platform provides full, code-level visibility into the performance of your PHP application built on the Kohana framework. With rapid installation and the most scalable #architecture in the industry, AppDynamics solutions help you deploy your #applications more quickly and with more confidence.

Read More


Last Restore Time of SQL server database

This article will guide you on how to collect #database restoration #history. The #SQL server database last restore time can be found using the system table in 'msdb'.
We get the following database #restoration history in my environment.
i. restore_date: It shows the database restoration #date.
ii. destination_database_name: We can get the destination database name using this #column.
iii. user_name: it gives user name that performed the restoration for that particular database.

Read More


Steps to deploy DACPAC with SSMS

This article will guide you on the steps to deploy DACPAC which involves registering a DAC instance by storing the DAC definition in the #msdb system database. 

A DAC is a self-contained unit of #SQL Server #database deployment that enables data-tier developers and database administrators to package SQL #Server objects into a portable artifact called a #DAC package, also known as a #DACPAC.

Read More


SQL server error 40 Tips to fix it

This article will guide you on the steps to fix #SQL Server Error 40 which is related to TCP/IP connection or Named Pipes connections. To avoid these types of errors use dynamic #ports when database engines have been configured

Read More


SQL server error 17 Steps to fix it

This article will guide you on the steps to fix 'SQL Server does not exist or access denied' error which occurs when the computer running #Microsoft #SQL Server is not reachable.

Read More


SQL Network Interfaces error 28 Steps to fix it

This article will guide you in fixing "SQL #Network #Interfaces #error 28" which happens while trying to connect to #SQL #Server instance either using #SSMS (SQL Server Management Studio) or using any other way.

Read More


SQL Server error 14265 How to fix

This article will guide you on the steps to fix SQL Server #error 14265 which occurs when the #SQL Server #Agent service auto restarts the SQL #Server.

Read More


SQL server error 1101

This article will guide on the steps to resolve #SQL SERVER ERROR "1101 : Could not allocate a new page for database because of insufficient #disk space in filegroup".

You can make sure there is enough Hard Disk space where #database files are stored on #server and Turn on AUTOGROW for file #groups.

Read More


Types of SQL server backups

This article will guide you on the different types of SQL Server backups and how to use them to run #SQL Server #backups to safeguard our #databases from user #errors, media failure, #hardware failure, and so on.

A full database backup backs up the whole database. This includes part of the #transaction #log so that the full database can be recovered after a full database backup is restored.

Read More


SQL error 15123

This article will guide you on the steps to troubleshoot and fix #SQL server #error #15123 which occurs in the process of changing or viewing the values of any advanced server configuration option.

Read More


Fix SQL error 824

This article will guide you through the steps to fix 824 error which is a logical Input/Output (I/O) error.

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


Using Ansible to copy MySQL databases

This article will guide us on how to perform database migration using Ansible as the controller which can help to copy a MySQL database from one remote server to another.

Read More


Solution to error sql72045

How to fix error sql72045 as soon as possible.

Read More