Changing @@version

Hi
I have Sql2000 Server , i want to change the @.@.version.
Can i change the result of SELECT @.@.version ?
Where can i do this ?
Paul
No you can't change it...it's a built in function.
-Sue
On Wed, 31 Aug 2005 04:29:01 -0700, "paul"
<paul@.discussions.microsoft.com> wrote:

>Hi
>I have Sql2000 Server , i want to change the @.@.version.
>Can i change the result of SELECT @.@.version ?
>Where can i do this ?
|||Hi,
No you cant manually change that. As soon as you install the service
pack/security updates the version is automatically updated.
Thanks
Hari
SQL Server MVP
"paul" <paul@.discussions.microsoft.com> wrote in message
news:26F0A282-D97C-4C78-BAB7-E9518F17E8D7@.microsoft.com...
> Hi
> I have Sql2000 Server , i want to change the @.@.version.
> Can i change the result of SELECT @.@.version ?
> Where can i do this ?
> --
> Paul
|||As the others stated, you cannot change @.@.version, or the values returned by
the other system functions whose names start with @.@.. Also, it would be very
confusing to DBAs or others if @.@.version on an instance of the database
engine started reporting something other than the version of the software.
What do you want to change? Do you want to pull parts of the information
out? If so, have a look at the SERVERPROPERTY function, different parameters
for that function report different parts of the information available in
@.@.version. Or maybe you could use SUBSTRING to pull out the part you're
interested in.
Alan Brewer [MSFT]
Content Architect, SQL Server Documentation Team
SQL Server Developer Center: http://msdn.microsoft.com/sql
SQL Server TechCenter: http://technet.microsoft.com/sql/
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi
I have a aplication (software) that only run if the answerd of the select
@.@.version is : MSDE SQL serrver... ..... .
But my aplication is already with 1,9 Gb , so if i change to SQL SERVER the
aplication will not run.
If i can use SQL Server and altered the result of @.@.version , to MSDE .....
, i think that the aplication will run .
Paul
"Alan Brewer [MSFT]" wrote:

> As the others stated, you cannot change @.@.version, or the values returned by
> the other system functions whose names start with @.@.. Also, it would be very
> confusing to DBAs or others if @.@.version on an instance of the database
> engine started reporting something other than the version of the software.
> What do you want to change? Do you want to pull parts of the information
> out? If so, have a look at the SERVERPROPERTY function, different parameters
> for that function report different parts of the information available in
> @.@.version. Or maybe you could use SUBSTRING to pull out the part you're
> interested in.
> --
> Alan Brewer [MSFT]
> Content Architect, SQL Server Documentation Team
> SQL Server Developer Center: http://msdn.microsoft.com/sql
> SQL Server TechCenter: http://technet.microsoft.com/sql/
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||I suggest you contact the software author or vendor for support. Safest
to assume there's a valid reason why such a constraint would be built
in to the software. For example maybe the vendor only licenses the
product for use with MSDE.
David Portas
SQL Server MVP

Changing @@version

Hi
I have Sql2000 Server , i want to change the @.@.version.
Can i change the result of SELECT @.@.version ?
Where can i do this ?
--
PaulNo you can't change it...it's a built in function.
-Sue
On Wed, 31 Aug 2005 04:29:01 -0700, "paul"
<paul@.discussions.microsoft.com> wrote:
>Hi
>I have Sql2000 Server , i want to change the @.@.version.
>Can i change the result of SELECT @.@.version ?
>Where can i do this ?|||Hi,
No you cant manually change that. As soon as you install the service
pack/security updates the version is automatically updated.
Thanks
Hari
SQL Server MVP
"paul" <paul@.discussions.microsoft.com> wrote in message
news:26F0A282-D97C-4C78-BAB7-E9518F17E8D7@.microsoft.com...
> Hi
> I have Sql2000 Server , i want to change the @.@.version.
> Can i change the result of SELECT @.@.version ?
> Where can i do this ?
> --
> Paul|||As the others stated, you cannot change @.@.version, or the values returned by
the other system functions whose names start with @.@.. Also, it would be very
confusing to DBAs or others if @.@.version on an instance of the database
engine started reporting something other than the version of the software.
What do you want to change? Do you want to pull parts of the information
out? If so, have a look at the SERVERPROPERTY function, different parameters
for that function report different parts of the information available in
@.@.version. Or maybe you could use SUBSTRING to pull out the part you're
interested in.
--
Alan Brewer [MSFT]
Content Architect, SQL Server Documentation Team
SQL Server Developer Center: http://msdn.microsoft.com/sql
SQL Server TechCenter: http://technet.microsoft.com/sql/
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi
I have a aplication (software) that only run if the answerd of the select
@.@.version is : MSDE SQL serrver... ..... .
But my aplication is already with 1,9 Gb , so if i change to SQL SERVER the
aplication will not run.
If i can use SQL Server and altered the result of @.@.version , to MSDE .....
, i think that the aplication will run .
Paul
"Alan Brewer [MSFT]" wrote:
> As the others stated, you cannot change @.@.version, or the values returned by
> the other system functions whose names start with @.@.. Also, it would be very
> confusing to DBAs or others if @.@.version on an instance of the database
> engine started reporting something other than the version of the software.
> What do you want to change? Do you want to pull parts of the information
> out? If so, have a look at the SERVERPROPERTY function, different parameters
> for that function report different parts of the information available in
> @.@.version. Or maybe you could use SUBSTRING to pull out the part you're
> interested in.
> --
> Alan Brewer [MSFT]
> Content Architect, SQL Server Documentation Team
> SQL Server Developer Center: http://msdn.microsoft.com/sql
> SQL Server TechCenter: http://technet.microsoft.com/sql/
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>|||I suggest you contact the software author or vendor for support. Safest
to assume there's a valid reason why such a constraint would be built
in to the software. For example maybe the vendor only licenses the
product for use with MSDE.
--
David Portas
SQL Server MVP
--

Changing @@version

Hi
I have Sql2000 Server , i want to change the @.@.version.
Can i change the result of SELECT @.@.version ?
Where can i do this ?
PaulNo you can't change it...it's a built in function.
-Sue
On Wed, 31 Aug 2005 04:29:01 -0700, "paul"
<paul@.discussions.microsoft.com> wrote:

>Hi
>I have Sql2000 Server , i want to change the @.@.version.
>Can i change the result of SELECT @.@.version ?
>Where can i do this ?|||Hi,
No you cant manually change that. As soon as you install the service
pack/security updates the version is automatically updated.
Thanks
Hari
SQL Server MVP
"paul" <paul@.discussions.microsoft.com> wrote in message
news:26F0A282-D97C-4C78-BAB7-E9518F17E8D7@.microsoft.com...
> Hi
> I have Sql2000 Server , i want to change the @.@.version.
> Can i change the result of SELECT @.@.version ?
> Where can i do this ?
> --
> Paul|||As the others stated, you cannot change @.@.version, or the values returned by
the other system functions whose names start with @.@.. Also, it would be very
confusing to DBAs or others if @.@.version on an instance of the database
engine started reporting something other than the version of the software.
What do you want to change? Do you want to pull parts of the information
out? If so, have a look at the SERVERPROPERTY function, different parameters
for that function report different parts of the information available in
@.@.version. Or maybe you could use SUBSTRING to pull out the part you're
interested in.
Alan Brewer [MSFT]
Content Architect, SQL Server Documentation Team
SQL Server Developer Center: http://msdn.microsoft.com/sql
SQL Server TechCenter: http://technet.microsoft.com/sql/
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi
I have a aplication (software) that only run if the answerd of the select
@.@.version is : MSDE SQL serrver... ..... .
But my aplication is already with 1,9 Gb , so if i change to SQL SERVER the
aplication will not run.
If i can use SQL Server and altered the result of @.@.version , to MSDE .....
, i think that the aplication will run .
Paul
"Alan Brewer [MSFT]" wrote:

> As the others stated, you cannot change @.@.version, or the values returned
by
> the other system functions whose names start with @.@.. Also, it would be ve
ry
> confusing to DBAs or others if @.@.version on an instance of the database
> engine started reporting something other than the version of the software.
> What do you want to change? Do you want to pull parts of the information
> out? If so, have a look at the SERVERPROPERTY function, different paramete
rs
> for that function report different parts of the information available in
> @.@.version. Or maybe you could use SUBSTRING to pull out the part you're
> interested in.
> --
> Alan Brewer [MSFT]
> Content Architect, SQL Server Documentation Team
> SQL Server Developer Center: http://msdn.microsoft.com/sql
> SQL Server TechCenter: http://technet.microsoft.com/sql/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>|||I suggest you contact the software author or vendor for support. Safest
to assume there's a valid reason why such a constraint would be built
in to the software. For example maybe the vendor only licenses the
product for use with MSDE.
David Portas
SQL Server MVP
--

Changes in Katmai

I've got a number of questions about the forthcoming release which hopefully can be answered:

1) What version of Excel will 2008 export too? Currently exported Excel files are in native 2000/2003 format. Please don't tell me they will only export in 2007 format!

2) Can you give any details on changes we can expect to the report viewer (web version) control? In particular will it behave better in an update panel? Also we have found the only way of getting the height property to set correctly with this control is to use some very (I'm mean very) dodgy java script. This seems to be a common problem looking through various forums.

3) Will we have the option of opening linked reports through the report viewer in a new window/tab (this is common complaint from my users currently).

4) In the code window of the report designer is there any chance of getting some IntelliSense?

5) Will there be support for stored procedures that return multiple recordsets?

Thanks

Simon

Hi Simon,

I can answer #1 of your questions. Reporting Services 2008 will export to the same Excel format as before. The XLS format can be used on Excel 2000-2007.

Best regards,
Chris|||

#5: It's not on the list for SSRS 2008.

Could you please explain in more detail why this is so important?

Can you write wrapper stored procedures that return a particular recordset you are interested in?

-- Robert

|||

Thanks for both the answers so far. In response to Robert's point about #5 - it's useful rather than requirement.

I worked recently on converting an ASP based reporting system into RS. Many of the existing procs returns multiple recordsets so we struggled to reuse the code. Agreed it could be done with a wrapper anyway. This certainly wouldn't stop me wanting to upgrade!

Any comments on the other points?

Thanks again

Simon

|||Robert,

I think support for multiple resultsets would be great.

At the moment we may have a report that shows the same basic data in more than one way, eg two tables and a chart. If a single resultset can't provide the data we need to execute more than one query from within the report. I appreciate that they can run in parallel, but if they are basically hitting the same underlying data it would be better for us to have one stored procedure that returned several resultsets.

This is especially true if the query can't be done in one statement and requires the production of temporary tables/variables. If we have to have separate queries we may have to recreate the temporary data in each query, whereas if we have one procedure with multiple resultsets it gets created just once and the second resultset can build on the first, the third on the second etc.

Regards,
Andrew

Changes in Katmai

I've got a number of questions about the forthcoming release which hopefully can be answered:

1) What version of Excel will 2008 export too? Currently exported Excel files are in native 2000/2003 format. Please don't tell me they will only export in 2007 format!

2) Can you give any details on changes we can expect to the report viewer (web version) control? In particular will it behave better in an update panel? Also we have found the only way of getting the height property to set correctly with this control is to use some very (I'm mean very) dodgy java script. This seems to be a common problem looking through various forums.

3) Will we have the option of opening linked reports through the report viewer in a new window/tab (this is common complaint from my users currently).

4) In the code window of the report designer is there any chance of getting some IntelliSense?

5) Will there be support for stored procedures that return multiple recordsets?

Thanks

Simon

Hi Simon,

I can answer #1 of your questions. Reporting Services 2008 will export to the same Excel format as before. The XLS format can be used on Excel 2000-2007.

Best regards,
Chris|||

#5: It's not on the list for SSRS 2008.

Could you please explain in more detail why this is so important?

Can you write wrapper stored procedures that return a particular recordset you are interested in?

-- Robert

|||

Thanks for both the answers so far. In response to Robert's point about #5 - it's useful rather than requirement.

I worked recently on converting an ASP based reporting system into RS. Many of the existing procs returns multiple recordsets so we struggled to reuse the code. Agreed it could be done with a wrapper anyway. This certainly wouldn't stop me wanting to upgrade!

Any comments on the other points?

Thanks again

Simon

|||Robert,

I think support for multiple resultsets would be great.

At the moment we may have a report that shows the same basic data in more than one way, eg two tables and a chart. If a single resultset can't provide the data we need to execute more than one query from within the report. I appreciate that they can run in parallel, but if they are basically hitting the same underlying data it would be better for us to have one stored procedure that returned several resultsets.

This is especially true if the query can't be done in one statement and requires the production of temporary tables/variables. If we have to have separate queries we may have to recreate the temporary data in each query, whereas if we have one procedure with multiple resultsets it gets created just once and the second resultset can build on the first, the third on the second etc.

Regards,
Andrew

Changes in Katmai

I've got a number of questions about the forthcoming release which hopefully can be answered:

1) What version of Excel will 2008 export too? Currently exported Excel files are in native 2000/2003 format. Please don't tell me they will only export in 2007 format!

2) Can you give any details on changes we can expect to the report viewer (web version) control? In particular will it behave better in an update panel? Also we have found the only way of getting the height property to set correctly with this control is to use some very (I'm mean very) dodgy java script. This seems to be a common problem looking through various forums.

3) Will we have the option of opening linked reports through the report viewer in a new window/tab (this is common complaint from my users currently).

4) In the code window of the report designer is there any chance of getting some IntelliSense?

5) Will there be support for stored procedures that return multiple recordsets?

Thanks

Simon

Hi Simon,

I can answer #1 of your questions. Reporting Services 2008 will export to the same Excel format as before. The XLS format can be used on Excel 2000-2007.

Best regards,
Chris|||

#5: It's not on the list for SSRS 2008.

Could you please explain in more detail why this is so important?

Can you write wrapper stored procedures that return a particular recordset you are interested in?

-- Robert

|||

Thanks for both the answers so far. In response to Robert's point about #5 - it's useful rather than requirement.

I worked recently on converting an ASP based reporting system into RS. Many of the existing procs returns multiple recordsets so we struggled to reuse the code. Agreed it could be done with a wrapper anyway. This certainly wouldn't stop me wanting to upgrade!

Any comments on the other points?

Thanks again

Simon

|||Robert,

I think support for multiple resultsets would be great.

At the moment we may have a report that shows the same basic data in more than one way, eg two tables and a chart. If a single resultset can't provide the data we need to execute more than one query from within the report. I appreciate that they can run in parallel, but if they are basically hitting the same underlying data it would be better for us to have one stored procedure that returned several resultsets.

This is especially true if the query can't be done in one statement and requires the production of temporary tables/variables. If we have to have separate queries we may have to recreate the temporary data in each query, whereas if we have one procedure with multiple resultsets it gets created just once and the second resultset can build on the first, the third on the second etc.

Regards,
Andrew

Changed Version of SQL Server

I have Windows 2000 Advanced Server with SQL Server 2000
with SP3A in a Active\Active Cluster.
When I loaded Windows 2000 SP4 on the server it changed
SQL Server 2000 version to "Microsoft SQL Server 2000 -
8.00.194 (Intel X86)".
If the Active (Node A)\ Active (Node B) cluster was moved
from original location could this change the SQL Server
version number. (Move Node A to Node B)
What could cause the version number to change within SQL
Server 2000. If the version is wrong is there away to
determine the version by SQL Server file dates?
Please help me resolve this issue.
Thanks,
Mark
weird normally the best way is to type the query below in Query Analyzer
which is determined by the version of SQLServr.exe.
SELECT @.@.VERSION
http://support.microsoft.com/default...b;en-us;321185
Although ocasionally (as with build 819 from
http://support.microsoft.com/default...b;en-us;826161) the real
version is not reflected as SQLServr.exe is not updated. In this case check
the registry @. HKLM\SOFTWARE\Microsoft\MSSQLServer\Hotfixes\0819
regards,
Andy.
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:024a01c48aea$87d32a80$a601280a@.phx.gbl...
>
> I have Windows 2000 Advanced Server with SQL Server 2000
> with SP3A in a Active\Active Cluster.
> When I loaded Windows 2000 SP4 on the server it changed
> SQL Server 2000 version to "Microsoft SQL Server 2000 -
> 8.00.194 (Intel X86)".
> If the Active (Node A)\ Active (Node B) cluster was moved
> from original location could this change the SQL Server
> version number. (Move Node A to Node B)
>
> What could cause the version number to change within SQL
> Server 2000. If the version is wrong is there away to
> determine the version by SQL Server file dates?
>
> Please help me resolve this issue.
> Thanks,
> Mark

Change version of SQL 2000 on running system

Hi,

is it possible to change the installed version on a server from SQL 2000 Standard Edition to SQL 2000 Developer Edition?

The server has been a production server and is now only used for testing by development, not from end users.

Best regards, Stefoon

I think the only supported way to do this is to uninstall and reinstall SQL 2000.

Thanks,
Sam Lester (MSFT)

|||Yes as you're downgrading the edition, but you can use the database without any issues with a backup.|||

Satya, what's the trick to change a current edition on a machine other than uninstall/reinstall?

Thanks,
Sam

Change version from SQL2K Developer Edition to SQL2K Standard Edition ?

Is there a "recipe" to do this ?
B.r.
Keld ThomsenJust upgrade!
"Keld Stig Thomsen" <dsl85271@.vip.cybercity.dk> wrote in message news:ckmnu6
$1mun$1@.news.cybercity.dk...
Is there a "recipe" to do this ?
B.r.
Keld Thomsen|||This type of "upgrade" is not supported according to the Online Books, Techn
et etc.
You can only upgrade an SQL2K Developer Edition to SQL2K Enterprise Edition
- NOT to Standard Edition:
http://msdn.microsoft.com/library/d.../>
ew_2xtf.asp
And that's why I'm asking for a 'recipe'.
Best regards
Keld Stig Thomsen
"TJ" <tunj@.hotmail.com> wrote in message news:uUvZyTlsEHA.3412@.TK2MSFTNGP14.
phx.gbl...
Just upgrade!
"Keld Stig Thomsen" <dsl85271@.vip.cybercity.dk> wrote in message news:ckmnu6
$1mun$1@.news.cybercity.dk...
Is there a "recipe" to do this ?
B.r.
Keld Thomsen

Change version from SQL2K Developer Edition to SQL2K Standard Edition ?

Is there a "recipe" to do this ?
B.r.
Keld Thomsen
Just upgrade!
"Keld Stig Thomsen" <dsl85271@.vip.cybercity.dk> wrote in message news:ckmnu6$1mun$1@.news.cybercity.dk...
Is there a "recipe" to do this ?
B.r.
Keld Thomsen
|||This type of "upgrade" is not supported according to the Online Books, Technet etc.
You can only upgrade an SQL2K Developer Edition to SQL2K Enterprise Edition - NOT to Standard Edition:
http://msdn.microsoft.com/library/de...rview_2xtf.asp
And that's why I'm asking for a 'recipe'.
Best regards
Keld Stig Thomsen
"TJ" <tunj@.hotmail.com> wrote in message news:uUvZyTlsEHA.3412@.TK2MSFTNGP14.phx.gbl...
Just upgrade!
"Keld Stig Thomsen" <dsl85271@.vip.cybercity.dk> wrote in message news:ckmnu6$1mun$1@.news.cybercity.dk...
Is there a "recipe" to do this ?
B.r.
Keld Thomsen