Davy's Blog » Uncategorized

SQL Server Locking – 31/03/2011

Davy — Thu, 17 Mar 2011 14:59:58 +0000

We are happy to announce the second event of 2011, SQL Server Locking: Take back control of SQL Server brought to you by Marc Mertens.
Since the beginning of RDBMS systems locking control has been taken away from the programmer. SQL Server has however many ways to let you control the locks placed and their duration.
This session discuss how SQL Server does locking and how you can control locking.

About Marc Mertens
Marc Mertens is a SQL Server and .NET trainer/consultant voor Global Knowledge. He has been working with SQL server from version 4.x up to the current version. His Microsoft Certifications are MSCA, MSCE, MCDBA, MCAD,MCSD and MCT. He has been a trainer for every aspect of SQL server, from building .net applications using ADO.NET and LINQ to BI solutions.

Agenda:

18:00: Registration

18:30: Session Start

21:00: Session End

Location:
Global Knowledge Belgium
Industriepark Mechelen Noord II
Zandvoortstraat 1
2800 Mechelen
Tel.: 015/27.65.35
Fax: 015/20.49.50

This Event is brought to you by Globalknowledge

Click here to register

Belgian SQL Server Day 2010 on December, 2nd

Davy — Thu, 07 Oct 2010 11:12:51 +0000

For the third successive year the Belgian SQL Server User Group (SQLUG.BE vzw) and Microsoft are teaming up to organize the yearly Belgian SQL Server Day.

After the successful event of last year, SQL Server Day 2010 will again be the biggest event focused exclusively on SQL Server in Belgium and Luxembourg. Join us for sessions on SQL Azure, SQL Server 2008 R2,the Microsoft Business Intelligence platform and connect with your peers.

You will be able to attend a lot of interesting sessions from experts like Donald Farmer, Chris Webb, Nico Jacobs, Wesley Backelant, Dirk Gubbels, Karel Coenye, Nico Verbaenen, Werner Geuens and Thomas Kejser.

This year SQL Server Day will take place at San Marco Village near Antwerp.

Full details can be found on www.sqlserverday.be

Cannot rename a report in SharePoint integrated mode.

Davy — Wed, 22 Sep 2010 17:38:31 +0000

Installing the report server in SharePoint integrated mode, really gives you the possibility to offer a great reporting frontend to your users. But a few days ago I came across a real nasty bug:

I just tried to rename one of the reports, what should be an easy thing to do, but I got this really weird error message:

System.Web.Services.Protocols.SoapException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. —> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. —> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors
at Microsoft.ReportingServices.WebServer.ReportingService2005Impl.GetItemDataSources(String Item, DataSource[]& DataSources)
at Microsoft.ReportingServices.WebServer.ReportingService2006.GetItemDataSources(String Item, DataSource[]& DataSources)

This error did not make any sense to me, so I looked into the Report Server Trace Log for more info and found this:

library!ReportServer_0-11!6028!07/01/2010-14:15:39:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database., ;

library!ReportServer_0-11!6c18!07/01/2010-14:15:39:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database., ;

library!ReportServer_0-11!6028!07/01/2010-14:15:59:: Call to GetPermissionsAction(http://hictatriuap017/sites/DashboardsICTRA/ReportsLibrary/SLA PRD/Report Management Summary.rdl).

library!ReportServer_0-11!6c18!07/01/2010-14:15:59:: Call to GetItemDataSourcesAction(http://hictatriuap017/sites/DashboardsICTRA/ReportsLibrary/SLA PRD/Report Management Summary.rdl).

library!ReportServer_0-11!6c18!07/01/2010-14:15:59:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database., ;

library!ReportServer_0-11!6c18!07/01/2010-14:15:59:: e ERROR: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. —> System.Data.SqlClient.SqlException: Cannot insert duplicate key row in object ‘dbo.Catalog’ with unique index ‘IX_Catalog’.

The statement has been terminated.

For every report in the report library, reporting services creates a record in the Catalog table of the report server database. But when you delete a report, that record doesn’t seem to be deleted.

The catalog table has a unique index on the column “path”, that contains the full path to the report. When I tried to rename the report, it failed because a previously (deleted) report existed with that same name.

You can work around this problem by changing the value of the path column of the old record.

If anyone has more details about this problem or maybe a solution, please leave a comment.

SQL Server Day 2009, now with a third track, fully focused on Development

Davy — Tue, 17 Nov 2009 14:59:51 +0000

We are very proud to announce you that, because of the huge success and because of the numerous registrations, we’ve added an additional track to our agenda, which makes SQL Server Day 2009 an entire day, jam-packed with technical sessions spread over 3 tracks, namely Business Intelligence, the SQL Data Platform and Development. 6 break-out sessions and a mix of the best national and international speakers will guarantee an extraordinary journey into the deepest secrets of your SQL Server environment.
From Policy Based Management, through Designing Effective aggregations in Analysis Services 2008, to Powerpivot (aka Gemini) and much, much more. We assure you that the subjects will help you and your enterprise reach a higher level in your BI and SQL Server environment.
All you need to do is visit sqlserverday.be where you can register, find details about the speakers as well as the session abstracts.
See you December 3th @ Utopolis Mechelen.

Connect to SSIS Service failed: Error loading type library/DLL

Davy — Fri, 18 Sep 2009 09:44:08 +0000

After installing SQL Server Integration Services on an existing 64-bit SQL Server, I was unable to connect to SSIS using Management Studio.

The database engine and Analysis Services was already installed on this server. I added the SSIS service without Service Pack and applied SP3 afterwards. When trying to connect, Management Studio returned the following error message:

Connect to SSIS Service on machine “ComputerName” failed:
Error loading type library/DLL.

I found the explanation in the following support article: KB919224

This problem occurs because the installer unregisters the 32-bit Dts.dll file when the installer installs the 64-bit Dts.dll file. The 64-bit Dts.dll file is installed together with SQL Server 2005 SP2. Additionally, the 64-bit Dts.dll file may be installed together with any SSIS hotfix package that contains the 64-bit Dts.dll file.

The solution is to reregister the 32-bit dll’s manually:

%windir%\syswow64\regsvr32 “%ProgramFiles(x86)%\Microsoft SQL Server\90\dts\binn\dts.dll”

%windir%\syswow64\regsvr32 “%ProgramFiles(x86)%\Microsoft SQL Server\90\dts\binn\MsDtsSrvrUtil.dll”

For more info and some variations on the same problem, goto KB919224