Re: How to keep SQL2000 in upgrade to R2

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Bill, Susan,

Thank you for your efforts and follow-up on this. What a wonderful answer
you've given. I'm not sure which question the "Yes" applies to. Here is my
last question:

Is SQL2000 able to stay in place and function while we upgrade to R2?

Do I understand that it's ok to keep SQL2000 in place while we upgrade to R2
so long as we don't install 2005?




""Bill Peng [MSFT]"" <v-bpeng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:evzbcM48HHA.5604@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi,

Susan and I just contacted our lead, and the final answer to your solution
is Yes.

You can keep R2 installation, subscribe downgrade media, and keep SQL 2000
without upgrade to SQL 2005.

Sincerely,

Bill Peng
MCSE 2000, MCDBA, CCNP, CCDA
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
=====================================================
The public newsgroup only focuses on SBS related technical issues, for
other Microsoft products, we recommend you to post to appropriate
newsgroup
to get most qualified responses.
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive notification. When responding to
posts via your newsreader, please "Reply to Group" so that others may
learn
and benefit from your issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
X-Tomcat-ID: 33954105
References: <OkviG116HHA.5212@xxxxxxxxxxxxxxxxxxxx>
<ys4dm436HHA.4100@xxxxxxxxxxxxxxxxxxxxxx>
<#Mjf#846HHA.4252@xxxxxxxxxxxxxxxxxxxx>
<#69FKbB8HHA.1900@xxxxxxxxxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: v-bpeng@xxxxxxxxxxxxxxxxxxxx ("Bill Peng [MSFT]")
Organization: Microsoft
Date: Thu, 06 Sep 2007 02:54:21 GMT
Subject: Re: How to keep SQL2000 in upgrade to R2
X-Tomcat-NG: microsoft.public.windows.server.sbs
Message-ID: <LU1g7ED8HHA.4100@xxxxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
Lines: 164
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:61124
NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182

Hi,

Just confirmed with our Product Team, and here's the reply:

======
If the customer has upgraded to SBS 2003 R2 Premium, then the customer is
indeed licensed to use SQL 2005 Workgroup.

If the customer's app vendor hasn't certified to run on SQL 2005 Workgroup
- then, he can exercise his downgrade rights, and get SQL 2000 Std media,
and use it alongside SBS 2003 R2.

Once the third party app vendor says their app will run on SQL 2005
Workgroup, the customer could start using the SQL 2005 Workgroup included
in SBS 2003 R2 Premium (and stop using SQL 2000 Std).
======

So you have to request the downgrade right SQL 2000 Standard version
media,
remove R2 and SQL 2005, and upgrade again when your software vendor is
ready for SQL 2005.

Technically speaking, it is OK to have R2 installed first, and SQL 2005
afterward.

Hope this helps.

Sincerely,

Bill Peng
MCSE 2000, MCDBA, CCNP, CCDA
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
=====================================================
The public newsgroup only focuses on SBS related technical issues, for
other Microsoft products, we recommend you to post to appropriate
newsgroup
to get most qualified responses.
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive notification. When responding to
posts via your newsreader, please "Reply to Group" so that others may
learn
and benefit from your issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
From: "wdsnews" <wdsnews.0640@xxxxxxxxxxxxxx>
References: <OkviG116HHA.5212@xxxxxxxxxxxxxxxxxxxx>
<ys4dm436HHA.4100@xxxxxxxxxxxxxxxxxxxxxx>
<#Mjf#846HHA.4252@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: How to keep SQL2000 in upgrade to R2
Date: Wed, 5 Sep 2007 16:45:05 -0700
Lines: 85
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Message-ID: <#69FKbB8HHA.1900@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
NNTP-Posting-Host: dns.oregoncity.com 71.39.159.33
Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:61095
X-Tomcat-NG: microsoft.public.windows.server.sbs

Susan

Is the requirement to stick with "all or nothing" only a licensing
requirement or is there also a technical problem? Technically, is
SQL2000
able to stay in place and function while we upgrade to R2?



"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
wrote in message news:%23Mjf%23846HHA.4252@xxxxxxxxxxxxxxxxxxxxxxx
With all due respect, no he can't. It's all or nothing.

If he needs sql 2000 he has to stay on SP1 without R2.

The r2 downgrade right is an entire "suite" downgrade right.

Bill Peng [MSFT] wrote:
Of course you can.

Just don't remove your Sharepoint instance, and only install R2
Technology on your SBS SP1 Server. Don't install Premium Tech which
contains SQL 2005.

At this point, you will just use the R2 SQL Server 2005 Downgrade
right.

There won't be any problem.

Sincerely,

Bill Peng
MCSE 2000, MCDBA, CCNP, CCDA
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
=====================================================
The public newsgroup only focuses on SBS related technical issues, for
other Microsoft products, we recommend you to post to appropriate
newsgroup to get most qualified responses.
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you
check
the "Notify me of replies" box to receive notification. When
responding
to posts via your newsreader, please "Reply to Group" so that others
may
learn and benefit from your issue.

Microsoft engineers can only focus on one issue per thread. Although
we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing so, it will ensure your issues are resolved in a timely manner.
For
urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
From: "wdsnews" <wdsnews.0640@xxxxxxxxxxxxxx>
Subject: How to keep SQL2000 in upgrade to R2
Date: Thu, 30 Aug 2007 16:27:03 -0700
Lines: 7
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Message-ID: <OkviG116HHA.5212@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
NNTP-Posting-Host: dns.oregoncity.com 71.39.159.33
Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.sbs:59902
X-Tomcat-NG: microsoft.public.windows.server.sbs

If we have SBS 2003 sp1 in place with SQL2000, is it possible to do
an
in-place upgrade to R2 while keeping SQL 2000 while we wait for our
vendor to update their application to SQL2005?














.



Relevant Pages

  • RE: Fax monitor incoming + outgoing calls?
    ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... When opening a new thread via the web interface, we recommend you check the ...
    (microsoft.public.windows.server.sbs)
  • Re: IIS logs for Exchange/OMA Access
    ... "Microsoft Exchange ActiveSync Administration". ... This newsgroup only focuses on SBS technical issues. ... When opening a new thread via the web interface, we recommend you check the ... <Server Error in '/MobileAdmin' Application. ...
    (microsoft.public.windows.server.sbs)
  • Re: Weird 529 Errors in Security Log
    ... For medium security requirement, the recommended configurations are: ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... When opening a new thread via the web interface, we recommend you check ...
    (microsoft.public.windows.server.sbs)
  • RE: HELP!!!!
    ... server in repair mode since the SBS server is DC that method will lost many ... Microsoft CSS Online Newsgroup Support ... When opening a new thread via the web interface, we recommend you check the ...
    (microsoft.public.windows.server.sbs)
  • RE: Received fax failure
    ... inbound faxes. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... When opening a new thread via the web interface, we recommend you check the ...
    (microsoft.public.windows.server.sbs)