(Microsoft.SqlServer.Management.UI.RSClient)

When connecting to Reporting Services (2005) using MS Management Studio I've had this message:

Connect to Server
Cannot connect to <ServerName>.

ADDITIONAL INFORMATION:

Unable to connect to the remote server (Microsoft.SqlServer.Management.UI.RSClient)

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.5:80 (System)

I could still connect to Reporting Services using Web interface.

I've noticed that for some reason Domain Controler does not translated server name to proper IP address, so quick fix was to use IP address while connecting, and everything was ok.

When i was trying to apply this hotfix using Windows Update it failed with Error Code 7342.

Workaround for me was to download it from here and install this hotfix manually.

SQL Server 2005 actually allows us to parameterize the TOP clause, using a variable, expression or statement. So you can do things like:

select top (@foo) [Column1] from [dbo].[myTable] 
 
select top (SELECT COUNT(*) FROM somewhere else) [Column1] from [dbo].[myTable]
 
select top (@foo + 5 * 4 / 2) [Column1] from [dbo].[myTable]

so we can create parameterized stored procedure with top as input parameter. In Sql 2005 it's simple:

create procedure dbo.getFoo 
    @top INT 
as 
begin 
    select top (@top) percent [column1]
        from [dbo].[myTable]         
end
go

However there are ways around it:

1. Don't use the VS SQL Server Project, but just create a normal class library project, add references as per usual and then manually create your assembly through CREATE ASSEMBLY. Make sure your referenced assemblies are in the same directory as your user assembly. The SQLCLR team has released some code that automatically creates procs/functions/triggers etc. when you run the CREATE ASSEMBLY code.

2. If you want to use the VS SQL Server Project you can create the assembly you want to reference in the database before you try to reference it. I.e: do a manual CREATE ASSEMBLY against the ManagedDTS.dll

3. Use my SQL Server VS templates and deploy task. This gives you the ability to reference what you want, and still get auto deployment. However, which-ever way to go, be careful with what you are doing. You don't want some code to compromise SQL Server!

The easiest way to be able to create an assembly as UNSAFE/EXTERNAL ACCESS you can do this:

1. Mark the database as trustworthy: ALTER DATABASE db_name SET TRUSTWORTHY ON 
2. Give the login of the owner of the database the right permissions: GRANT EXTERNAL ACCESS ASSEMBLY to userlogin.

That's it. You can now create an assembly as EXTERNAL ACCESS/UNSAFE. 

When you try to install Microsoft SQL Server 2005 on a Windows Web Server 2008-based system, the installation is not completed successfully. Additionally, you receive the following warning message:

SQL Server Edition Operating System Compatibility (Warning) Messages

"SQL Server Edition Operating System Compatibility Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online. "

To resolve this problem, download and install the appropriate hotfix:

Windows 2008 32-bit edition

Windows 2008 64-bit edition

Then everything seems to install ok.