SQL Server Reporting Server Authentication Error

Blogger Tags: sql server reporting services authenticatiion exception

After installing Reporting Services on a Windows 2003 Server SP1 Box, everything seems to be ok, but when i browse to the Reports website: http://localhost/Reports i've got the following error message: HTTP status 401: Access Denied.

After some Google search i found that this is not a problem related to MS Reporting Servers, but it's an issue related to Windows 2003 Service Pack 1.

If you have this problem, and you have a box with Windows 2003 with SP1, follow these steps to fix it.

1.Click Start, click Run, type regedit, and then click OK.

2.In Registry Editor, locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

3.Right-click Lsa, point to New, and then click DWORD Value.

4.Type DisableLoopbackCheck, and then press ENTER.

5.Right-click DisableLoopbackCheck, and then click Modify.

6.In the Value data box, type 1, and then click OK.

7.Quit Registry Editor, and then restart your computer.

 

You can find more details here: http://support.microsoft.com/kb/896861/

Community Server Tags: sql server;reporting services;authenticatiion;exception

Shrink SQL Server transaction log files

Once I'm using database mirroring, all my databases has the recovery model set to Full.

When using this recovery model, you must have a good backup policy to regularly backup your transaction log, between full backups of your database. If not, the database transaction log file size may increase a lot.

To shrink the file size I use the following script:

exec sp_dboption DBName, 'trunc. log on chkpt.', true

checkpoint

DBCC SHRINKFILE (DBNameFileName, 500);

exec sp_dboption DBName, 'trunc. log on chkpt.', false

Sql Server Database Mirror and Recovery Model

When i've configured the Database Mirroring on my production environment, i've changed the database recovery model to full. Then, i've faced the issue with transaction log file size, that is increasing a lot, on all mirrored databases.

After some research, I found some information to solve this that i would like to share with you.

To prevent the transaction log files from growing unexpectedly, consider using one of the following methods:

• Set the size of the transaction log files to a large value to avoid the automatic expansion of the transaction log files.

• Configure the automatic expansion of transaction log files by using memory units instead of a percentage after you thoroughly evaluate the optimum memory size.
For additional information about the issues to consider when you configure the autogrow option, click the following article number to view the article in the Microsoft Knowledge Base:

315512 (http://support.microsoft.com/kb/315512/) Considerations for autogrow and autoshrink configuration

• Change the recovery model. If a disaster or data corruption occurs, you must recover your database so that the data consistency and the transactional integrity of the database are maintained. Based on how critical the data in your database is, you can use one of the following recovery models to determine how your data is backed up and what your exposure to the data loss is:

•Simple recovery model

•Full recovery model

•Bulk-logged recovery model

By using the simple recovery model, you can recover your database to the most recent backup of your database. By using the full recovery model or the bulk-logged recovery model, you can recover your database to the point when the failure occurred by restoring your database with the transaction log file backups.
By default, in SQL Server 2000 and in SQL Server 2005, the recovery model for a SQL Server database is set to the Full recovery model. With the full recovery model, regular backups of the transaction log are used to prevent the transaction log file size from growing out of proportion to the database size. However, if the regular backups of the transaction log are not performed, the transaction log file grows to fill the disk, and you may not be able to perform any data modification operations on the SQL Server database.
You can change the recovery model from full to simple if you do not want to use the transaction log files during a disaster recovery operation.

• Back up the transaction log files regularly to delete the inactive transactions in your transaction log.

• Design the transactions to be small.

• Make sure that no uncommitted transactions continue to run for an indefinite time.

• Schedule the Update Statistics option to occur daily.

• To defragment the indexes to benefit the workload performance in your production environment, use the DBCC INDEXDEFRAG Transact-SQL statement instead of the DBCC DBREINDEX Transact-SQL statement. If you run the DBCC DBREINDEX statement, the transaction log may expand significantly when your SQL Server database is in Full recovery mode. Additionally, the DBCC INDEXDEGRAG statement does not hold the locks for a long time, unlike the DBCC DBREINDEX statement.
For additional information about defragmenting the indexes in SQL Server 2000, see the following Microsoft Web site:

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx (http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx)

If you must run the DBCC DBREINDEX statement as a job that is a part of the database maintenance plan, you must break up the job into multiple jobs. Additionally, you must take the frequent backups for the transaction logs between the execution of the jobs.

You can see the full document on the following address. http://support.microsoft.com/kb/873235

Kill all SQL active connections

For the last couple of weeks i'm using SSIS a lot. In some tasks i need to make sure that any client is connected to the database where i need to perform a specific task.

To solve this issue i found this script that basically, kills all the active connections on the database.

DECLARE 
@p_SPID int, 
@p_SQL nvarchar(2000),
@dbName nvarchar(100)

SET @dbName = 'MyDBName'

DECLARE #cur_Processes CURSOR FOR 

SELECT 
p.SPID 
FROM 
master.dbo.sysprocesses AS p 
JOIN master.dbo.sysdatabases AS d ON( d.dbid = p.dbid ) 
WHERE 
d.Name = @dbName AND p.SPID > 50 -- AND spid >= 51 (because spids of 50 or less are reserved for internal use.) 
OPEN #cur_Processes 
FETCH NEXT FROM #cur_Processes INTO @p_SPID 
WHILE @@FETCH_STATUS = 0 

BEGIN 
SET @p_SQL = 'KILL ' + CONVERT( nvarchar(30), @p_SPID ) 
PRINT @p_SQL 
EXECUTE( @p_SQL ) 
FETCH NEXT FROM #cur_Processes INTO @p_SPID 
END 
CLOSE #cur_Processes 
DEALLOCATE #cur_Processes