My org has a new SQL Server 2005 server and we've just installed a new
commercial database. After the consultant installed the db, I had a
good look around and realised it's set to a lower compatibility level.
The company that sourced the database assures us that it's 'fully
supported within a SQL Server 2005 environment'.
I trust that the application itself works fine as configured, but am
worried that we'll run into issues when we want to configure Reporting
Services and log shipping later in the year. I've done a bit of
research and it seems we won't have access to 'new' SS2005 features,
such as the database diagram tool and the new TABLESAMPLE clause, and
that the server will parse T-SQL differently depending on what
compatability level the database is set to. But I've yet to find how
(whether) this will affect things log shipping and Reporting Services.
Can anyone shed some light on this for me? I'd want this noted as
outstanding issue that they need to sort (our request for tender docs
specified SQL Server 2005 compatibility), but they seem to think it
meets this requirement even though it's running at a lower
compatibility level. I'd like to have some examples of SQL Server 2005
functions that we won't be able to use because of this.
Much appreciated.Yes - there are some features that will not work in compatibility mode.
Many of the neat performance reports in SSMS are not able to collect data on
databases in earlier compatibility mode. Compatibility mode is geared
towards syntax compatiblity and not as much about behavior compatibility.
This is because fundamentally, the engine has changed and will not emulate
the exact same behavior.
I do not recall seeing a link about all of the features that are affected by
this, but since compatibility mode is a database-level setting, you can
create a dummy DB at the desired db compat level and test it out.
Hope this helps!
Rick Heiges
SQL Server MVP
"RJGiskard" <rjgiskard@.googlemail.com> wrote in message
news:cd79f4ec-3464-41ee-ab75-a9450f8a735f@.d21g2000prf.googlegroups.com...
> My org has a new SQL Server 2005 server and we've just installed a new
> commercial database. After the consultant installed the db, I had a
> good look around and realised it's set to a lower compatibility level.
> The company that sourced the database assures us that it's 'fully
> supported within a SQL Server 2005 environment'.
> I trust that the application itself works fine as configured, but am
> worried that we'll run into issues when we want to configure Reporting
> Services and log shipping later in the year. I've done a bit of
> research and it seems we won't have access to 'new' SS2005 features,
> such as the database diagram tool and the new TABLESAMPLE clause, and
> that the server will parse T-SQL differently depending on what
> compatability level the database is set to. But I've yet to find how
> (whether) this will affect things log shipping and Reporting Services.
> Can anyone shed some light on this for me? I'd want this noted as
> outstanding issue that they need to sort (our request for tender docs
> specified SQL Server 2005 compatibility), but they seem to think it
> meets this requirement even though it's running at a lower
> compatibility level. I'd like to have some examples of SQL Server 2005
> functions that we won't be able to use because of this.
> Much appreciated.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment