If SQL 2000 must access a 2005 database continually, does it require setting
the compatibility to 8.0? What are the consequences of setting the 2005
database to 9.0 under these circumstances? (Trying to get cross apply to
work with 8.0 compatibility set on SQL 2005).
Regards,
Jamie
Got it... fire off from master which will use version 9.0 irregardless of
server setting.
Regards,
Jamie
"thejamie" wrote:
> If SQL 2000 must access a 2005 database continually, does it require setting
> the compatibility to 8.0? What are the consequences of setting the 2005
> database to 9.0 under these circumstances? (Trying to get cross apply to
> work with 8.0 compatibility set on SQL 2005).
> --
> Regards,
> Jamie
|||That's a useful tidbit there!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:845339A7-B70C-4BEB-B556-2C3F061318D1@.microsoft.com...[vbcol=seagreen]
> Got it... fire off from master which will use version 9.0 irregardless of
> server setting.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:
Showing posts with label continually. Show all posts
Showing posts with label continually. Show all posts
Tuesday, February 14, 2012
Cross apply requires 9.0 compatibility
If SQL 2000 must access a 2005 database continually, does it require setting
the compatibility to 8.0? What are the consequences of setting the 2005
database to 9.0 under these circumstances? (Trying to get cross apply to
work with 8.0 compatibility set on SQL 2005).
--
Regards,
JamieGot it... fire off from master which will use version 9.0 irregardless of
server setting.
--
Regards,
Jamie
"thejamie" wrote:
> If SQL 2000 must access a 2005 database continually, does it require setti
ng
> the compatibility to 8.0? What are the consequences of setting the 2005
> database to 9.0 under these circumstances? (Trying to get cross apply to
> work with 8.0 compatibility set on SQL 2005).
> --
> Regards,
> Jamie|||That's a useful tidbit there!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:845339A7-B70C-4BEB-B556-2C3F061318D1@.microsoft.com...[vbcol=seagreen]
> Got it... fire off from master which will use version 9.0 irregardless of
> server setting.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:
>
the compatibility to 8.0? What are the consequences of setting the 2005
database to 9.0 under these circumstances? (Trying to get cross apply to
work with 8.0 compatibility set on SQL 2005).
--
Regards,
JamieGot it... fire off from master which will use version 9.0 irregardless of
server setting.
--
Regards,
Jamie
"thejamie" wrote:
> If SQL 2000 must access a 2005 database continually, does it require setti
ng
> the compatibility to 8.0? What are the consequences of setting the 2005
> database to 9.0 under these circumstances? (Trying to get cross apply to
> work with 8.0 compatibility set on SQL 2005).
> --
> Regards,
> Jamie|||That's a useful tidbit there!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:845339A7-B70C-4BEB-B556-2C3F061318D1@.microsoft.com...[vbcol=seagreen]
> Got it... fire off from master which will use version 9.0 irregardless of
> server setting.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:
>
Labels:
access,
apply,
compatibility,
consequences,
continually,
cross,
database,
microsoft,
mysql,
oracle,
requires,
server,
setting,
settingthe,
sql
Cross apply requires 9.0 compatibility
If SQL 2000 must access a 2005 database continually, does it require setting
the compatibility to 8.0? What are the consequences of setting the 2005
database to 9.0 under these circumstances? (Trying to get cross apply to
work with 8.0 compatibility set on SQL 2005).
--
Regards,
JamieGot it... fire off from master which will use version 9.0 irregardless of
server setting.
--
Regards,
Jamie
"thejamie" wrote:
> If SQL 2000 must access a 2005 database continually, does it require setting
> the compatibility to 8.0? What are the consequences of setting the 2005
> database to 9.0 under these circumstances? (Trying to get cross apply to
> work with 8.0 compatibility set on SQL 2005).
> --
> Regards,
> Jamie|||That's a useful tidbit there!
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:845339A7-B70C-4BEB-B556-2C3F061318D1@.microsoft.com...
> Got it... fire off from master which will use version 9.0 irregardless of
> server setting.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:
>> If SQL 2000 must access a 2005 database continually, does it require
>> setting
>> the compatibility to 8.0? What are the consequences of setting the 2005
>> database to 9.0 under these circumstances? (Trying to get cross apply to
>> work with 8.0 compatibility set on SQL 2005).
>> --
>> Regards,
>> Jamie
the compatibility to 8.0? What are the consequences of setting the 2005
database to 9.0 under these circumstances? (Trying to get cross apply to
work with 8.0 compatibility set on SQL 2005).
--
Regards,
JamieGot it... fire off from master which will use version 9.0 irregardless of
server setting.
--
Regards,
Jamie
"thejamie" wrote:
> If SQL 2000 must access a 2005 database continually, does it require setting
> the compatibility to 8.0? What are the consequences of setting the 2005
> database to 9.0 under these circumstances? (Trying to get cross apply to
> work with 8.0 compatibility set on SQL 2005).
> --
> Regards,
> Jamie|||That's a useful tidbit there!
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:845339A7-B70C-4BEB-B556-2C3F061318D1@.microsoft.com...
> Got it... fire off from master which will use version 9.0 irregardless of
> server setting.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:
>> If SQL 2000 must access a 2005 database continually, does it require
>> setting
>> the compatibility to 8.0? What are the consequences of setting the 2005
>> database to 9.0 under these circumstances? (Trying to get cross apply to
>> work with 8.0 compatibility set on SQL 2005).
>> --
>> Regards,
>> Jamie
Labels:
access,
apply,
compatibility,
consequences,
continually,
cross,
database,
microsoft,
mysql,
oracle,
requires,
server,
setting,
sql
Subscribe to:
Posts (Atom)