Explore information related to mssql error
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.
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.
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.
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.
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.
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
