SQL 2005 JDBC Driver and Database Mirroring

We ran into some interesting situations with the SQL 2005 JDBC Driver (v1.2) and it’s use with failover partners. Take the following connection string: jdbc:sqlserver://myserver1;databaseName=AdventureWorks;failoverPartner=myserver2; In this connection string, our Primary server will be myserver1 with our failover server being myserver2.  If the primary server becomes unresponsive, we will fail over to the myserver2.  This…

6

Failure to load Report Manager due to truncated UserAgent string

We came across an issue when trying to load Report Manager.  We would get the following exception: System.ArgumentException: Version string portion was too short or too long. at System.Version..ctor(String version) at System.Web.Configuration.HttpCapabilitiesBase.GetClrVersions() at System.Web.Configuration.HttpCapabilitiesBase.get_ClrVersion() at Microsoft.ReportingServices.Common.RBRequirements.get_ClientMeetsRequirements() at Microsoft.ReportingServices.UI.FolderItems.GetReportBuilderLaunchUrl() In turn, this prevented Report Manager from loading.  The exception itself is occuring within the .NET Framework,…

2

Using SQLIOSim to Diagnose SQL Server Reported Checksum (Error 824/823) Failures

This is an extension to by previous post about SQLIOSim data integrity testing. http://blogs.msdn.com/psssql/archive/2008/03/05/how-it-works-sqliosim-checksums.aspx SQLIOSim (.exe/.com) is the predecessor to SQLIOStress.  SQLIOSim is SQL Server independent utility, generating both SQL Server and random I/O patterns. Demonstration SQLIOSim demonstration by rdorr (Larger Video Sizes: http://communityclips.officelabs.com/Video.aspx?videoId=f544ffcc-c92c-4506-8f3d-9f37365768aa) SQLIOSim is NOT designed to be a performance testing utility as…

2

SQL Server (2005 and 2008) Trace Flag 1118 (-T1118) Usage

Trace flag 1118 forces uniform extent allocations instead of mixed page allocations.   The trace flag is commonly used to assist in TEMPDB scalability by avoiding SGAM and other allocation contention points. SQL Server 2008 optimized mixed extent allocation behavior reducing the need for trace flag 1118 and the contention on SGAM(s).   The logic was also…

3

How It Works: SQL Server No Longer Uses RDTSC For Timings in SQL 2008 and SQL 2005 Service Pack 3 (SP3)

Many of you have encountered the RDTSC timing variances that I outlined in an earlier blog post:   http://blogs.msdn.com/psssql/archive/2006/11/27/sql-server-2005-sp2-will-introduce-new-messages-to-the-error-log-related-to-timing-activities.aspx and http://blogs.msdn.com/psssql/archive/2007/08/19/sql-server-2005-rdtsc-truths-and-myths-discussed.aspx  Several years ago SQL Server 2008 builds removed pure RDTSC, microsecond timings and replaced them with an MMTIME like, timing mechanism.   The timer (see timeGetTime for similar documentation) removes variances that can be experienced by…

3

How It Works: SQL Trace and MARS Connections

MSDN, TechNet, Books Online and other sources outline what Multiple Active Result Sets (MARS) is, how to use it and transaction scopes.   Working on an issue this week I found I needed to understand what the trace looked like.  In doing so I found the following helpful. The trace column (RequestId) represents the logical connection…

1

INF: RML Utilities: Turning on Trace Flags

Summary When using the RML utilities the logged message or documentation can indicate that use of a trace flag is necessary to change behavior. More Information The RML Utilities use command line parameter (-T) as a trace flag to alter the utilities behavior.  The term trace flag is a hold over from the SQL Server…

1

Should I run SQLIOSim? – An e-mail follow-up from SQL PASS 2008

From: Robert Dorr [mailto:rdorr@microsoft.com] Sent: Thursday, November 20, 2008 11:29 AM To: A SQL PASS MEMBER – CSS First Aid Station Question About SQLIOSim As we discussed at SQL PASS – SQLIOSim is an independent utility and has been used as part of the Windows Hardware Compatibility Testing (WHCL) suite for several years.   Many of…

5

RSWindowsNegotiate and 401.1 Error when using RS 2008

While I was setting up one of my demos for SQL PASS, I starting hitting 401.1 errors.  I was setting up a SharePoint Intergrated setup with Reporting Services. I knew I had a distributed environment, so I accounted for my Kerberos configuration.  I lined up my SPNs and made sure my accounts were trusted for…

1