Categories
Troubleshooting

DotNet 3.5 on Windows 7 to Install SQL Server 2008

This is a quick post to install or enable .Net 3.5 on windows 7. Last couple of weeks Im seeing more questions on installing SQL Server 2008 in windows 7 and the users are unable to install SQL Server 2008 pre-requisite (.Net 3.5 ). To Install SQL Server 2008, windows installer 4.5 & .Net 3.5 is required. Windows installer 4.5 is installed and enabled by default, .Net 3.5 is included in windows features, so you can directly go there and turn on .Net 3.5, windows 7 will automatically install this. To turn on .Net 3.5 in Windows 7 just follow the steps below

Categories
Troubleshooting

Troubleshooting Login failed Error 18456

Input : select * from sys.sysmessages where error = 18456

Output: Login failed for user ‘%.*ls’.%.*ls%.*ls

This is one of the infamous error message (and number) that most of the DBAs and developers have come across while working on SQL server. This message simply denotes that the client call was able to reach the SQL server and then an ACCESS was denied to the particular login for a reason. To figure out the exact reason, this error number 18456 with its STATE number is logged into the SQL server error log file, if SQL server was allowed or configured to capture the failed logins.

Categories
Troubleshooting

Error: 7139, Severity: 16, State: 1

Last week in our company we have started facing some error while uploading documents to the table. We have an database in which we will be uploading all the documents related to the customers, when the user tries to upload the document he she gets the error message as shown below

Categories
Troubleshooting

Log file growth in SQL Server

Each database in SQL Server contains at least one data file and one transaction log file. The transaction log file stores the details of all the modifications that are performed in the SQL Server database. If the transaction log file in a SQL Server database has grown enormously and if you have set the option for the transaction log files to grow automatically, the transaction log file grows in units of virtual log files.

Categories
Troubleshooting

How to Recover from Suspect Database

Many DBAs would have seen the database marked as suspect. If a database is marked suspect it cannot be accessed and hence nothing can be performed in the database. In this article I am going to explain how to overcome this and bring the database back to normalcy. There are three possible Workarounds to bring the database online and to retrieve the data. First try the Workaround 1 and if it fails go to Workaround 2 if that doesn’t yield the desired result try the Workaround 3.