Home » SQL Errors (Page 3)

Category Archives: SQL Errors

2013 with You & SQL Server

The WordPress.com stats helper monkeys prepared a 2013 annual report for this blog. Here’s an excerpt: The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 41,000 times in 2013. If it were a concert at Sydney Opera House, it would take about 15 sold-out performances for that many … Continue reading

Backup not starting for Database with Full Text Catalog…………..Failed to change the status to RESUME for full-text catalog in database. Error: 0x80043607

Issue :- One of our Database with Full Text Catalog is not getting backed up. When I checked, backup keeps pending on 0% without any progress. In SQL server error log, I also found error related to Full text catalog that SQL server is facing issue in setting Full test catalog status. These is some … Continue reading

Refresh Intellisense in SSMS(SQL Server Management Studio) 2008 & above

Intellisense is a new feature that comes with SSMS(SQL Server Management Studio) 2008 onwards. Intellisense makes coding quite easy. But Sometimes I find that intellisense becomes stale and you start getting the wavy red lines when writing code. Even though object exists in database but Intellisense is not able to recognize it. Refreshing the cache … Continue reading

Microsoft SQL Server License Helpline

Microsoft SQL Server license has lots of flavors in terms of user based \ CAL or processor based license, license based on versions or license based on environment (physical or virtual). Although, Microsoft release license guidelines for each & every SQL server version. But there are more complex scenarios for licensing then we think. Best … Continue reading

The server principal “xxxx” is not able to access the database “msdb” under the current security context.

Problem : Yesterday Night, One of my team member called & report that some users are getting below error no. 1 while connection to SQL server & error no. 2 while trying to open Management folder. Error 1 : Cannot display policy health state at the server level, because the user doesn’t have permission. Permission … Continue reading

%d bloggers like this: