Friday, November 20, 2009

Could not find stored procedure 'sp_filestream_configure'

Filestream is a new feature that came along with SQL Server 2008. You need to enable FileStream before using it.

If you google, syntax for enabling FileStream is EXEC sp_filestream_configure @enable_level = 3;

However, you will end-up with Could not find stored procedure 'sp_filestream_configure' error.

Above syntax if for CTPs not for RTM!. So the correct syntax follows.

USE master;

EXEC sys.sp_configure N'filestream access level', N'2'




Wednesday, November 18, 2009

An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode

Following error is occurring while trying to access report server or report manager in SQL Server Reporting Service 2005.

An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode

Reporting Services in SQL Server 2005 runs as on IIS 7.0. After configuring Reporting Service, two virtual directories will be created by default their Application pool is DefaultAppPool.

Every Application pool has Pipeline mode and there are two types of Pipeline modes namely, Integrated and Classic.

If the Pipeline mode of the Application Poll attached to virtual servers is Integrated you will get the above error.

You need to change the Integrated to Classic as shown below in IIS.


You do not have to restart neither IIS nor SQL Server Reporting Services.

There is another method. You need to create new application pool with Classic and attached that Application pool to the both virtual servers from Reporting Server Configuration Tool.

Friday, November 13, 2009

Spelling Mistake in Back Up Database Task of SSIS

In the SSIS task there are Maintenance Plan Tasks. Under the Maintenance Plan Tasks, there is a task called Back Up Database Task to backup databases. After drag and dropping the task to the control flow, press F4 to get properties. There is a property called TaskAllowsDatabaseSelection which is mis-spelled as shown in the following image.


Monday, November 2, 2009

Is SQL Server's latest security hole a real threat?

Last week Sentrigo brought a security hole in SQL Server to my attention. The issue is simply that SQL Server stores passwords in clear text in memory, so it’s quite possible to sniff the memory to retrieve passwords of other users. That in itself doesn’t sound dangerous at first glance because you have to have system admin rights in the database to do this. However, there are two basic situations where this could be horrendous.

Because most users have the same password, once you gain access to this password, you’ve gained access to all the boxes that account is on. This works on only native SQL passwords, not on Windows passwords. This is because when you use a Windows account to log into SQL, you don’t give it a password; you only pass in your security token, and there’s no password to steal. With SQL passwords, however, you pass in the SQL username and password, and this combination is stored in clear text in memory.

read more

Encryption, Decisive Factor to lose the WWII

Germany and Japan were gaining momentum to win world war II and concur the world. Some crucial decisions have changed the complexity of the ...