Did MS has some solution recommended for this reportServer blocking while running reports?

Thanks

Hi,

Both the System & ReportServer & ReportServerTempDB have same collation settings SQL_Latin1_General_CP1_CI_AS. The reports are working fine but when reporting services backgorund process runs, I'm seeing the collation conflict as...

could you please advice!!

The disk I backup the databases is on Primary and I did NOT see any errors on primary when this restore is failed on secondary. Everything seems fine on backup...

I went through the below link http://www.sqlservercentral.com/Forums/Topic795626-150-1.aspx

But I'm NOT considering to change ISOLATION level. Looking for other options

We also have the same problem. After analyzing the PL/SQL code,...

If you have that log backup on primary and secondary, check it out on the primary as well.

If its ok on the primary it was corrupted by the copy...

Thanks George,

But I'm more interested to know what caused the restore failure and prevent it to happen again. Because it's a big database of size 50 GB and it...

Hi Steve, Jason,

Are you guys do the Full/Diff/log backups to local server or backup to a Network Share?

If you backup local to the server, then if the server goes down...

We are using the same setup for SSRS and also seeing the blocking from report server. It's NOT from the PL/SQL code, but from report server on the SQL...

I got resolved this by performing the steps mentioned in Method1 from the link

http://support.microsoft.com/default.aspx?scid=kb;en-us;896861

But I have a question here:

1. Is this change going to effect any security...

I came to know that it's a wild card certificate and we can use any name in place of * in the certificate name *.abc.com

So I have used server name...

Any help would be appreciated..

Thanks

1

) Reporting Services (RS) is required for the Upgrade Advisor

This is a logical gotcha that kinda makes me mad. Microsoft Best Practices and our corporate security guidelines state that you...

Hi,

I went through the link http://msdn.microsoft.com/en-us/library/ms190730(SQL.90).aspx

where it says "Locking pages in memory is not required on 64-bit operating systems"

Now I'm confused what to do. Because, I already enabled...

SSIS was only required in SQL Server 2005 RTM - after SP1 the requirement for SSIS was removed. If you are not going to be running SSIS packages on that...