RE: Migration to SQL 2005 for Workgroups
- From: Gilbert <Gilbert@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 31 Oct 2006 07:55:02 -0800
Actually, I'm not sure that you read my post correctly. As I was saying,
I've already migrated it successfully. I just had some additional questions
after the migration. Please re-read my post and my questions below. Thank
you.
"chace zhang" wrote:
Hi,.
Thank you for posting here.
From your post, I understand you want to upgrade to SBS SQL 2005 on SBS R2.
If I'm off base, please do not hesitate to let me know.
Technical speaking on SBS server, there are already 2 instances using MSDE
to store SharePoint (Companyweb) uses the MSSQL$SharePoint database, while
the Monitoring features use the MSSQL$SBSMonitoring database to store data.
Both of these features are mutually exclusive for the most part.
You could (and you should) upgrade the SharePoint named instance to full
SQL from MSDE to SQL 2005.
Note: You cannot upgrade the Monitoring instance to SQL
Actually, the detailed installation instructions have already been
integrated into the sqlinstallsteps.htm file in the SBS 2k3 R2 Premium CD
root folder,
Upgrade the SHAREPOINT instance of WMSDE to SQL 2005 Work Group Edition.
" To prepare the http://companyweb Web site
" To create the SQL Server 2005 Workgroup Edition SHAREPOINT instance
" To configure permissions for the new SHAREPOINT instance of SQL Server
2005
" To turn on full-text search in Windows SharePoint Services
The following article describes the detailed steps, screenshots and some
additional tips for upgrading SharePoint instance to SQL 2005:
SBS 2003 R2 - Upgrading the SharePoint instance to SQL 2005
http://www.smallbizserver.net/tabid/266/articleType/ArticleView/articleId/21
1/Default.aspx
You can download the PDF for offline reading here:
http://www.smallbizserver.net/tabid/228/Default.aspx
Hope this helps, if you need more help on this issue, please do not
hesitate to let me know.
Have a nice day!
Best Regards,
Chace Zhang (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
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 e-mail notifications when there are
any updates in your thread. 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 CSS 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.
--------------------
| Thread-Topic: Migration to SQL 2005 for Workgroups
| thread-index: Acb8W1Sar8+j09z/QxOBWFMEvAttOA==
| X-WBNR-Posting-Host: 198.237.17.1
| From: =?Utf-8?B?R2lsYmVydA==?= <Gilbert@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Migration to SQL 2005 for Workgroups
| Date: Mon, 30 Oct 2006 11:41:01 -0800
| Lines: 19
| Message-ID: <54BF66A2-65DA-4EF5-932C-FB7C310DE81B@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:309114
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi,
|
| I've installed Small Business Server 2003 including the Premium and the
R2
| technologies. I followed the step by step instructions on migrating the
| Sharepoint from MSDE to SQL 2005.
|
| It migrated successfully, however when I ran the installation for Backup
| Exec, it told me that there was still a database SHAREPOINT that was
still on
| MSDE SQL 2000 without any service packs. It said it was a security risk.
It
| did show the other 2 databases (MONITORING and WSUS as having been
upgraded
| to SP3)
|
| I have a couple of quesitons:
|
| 1. How can I tell that SHAREPOINT is completely using SQL 2005 for
| Workgroups?? (and there aren't any remnants still hanging around)
|
| 2. How can I tell that SHAREPOINT is working correctly? (I can access
the
| company website http://companyweb).
|
- Follow-Ups:
- RE: Migration to SQL 2005 for Workgroups
- From: chace zhang
- RE: Migration to SQL 2005 for Workgroups
- Prev by Date: Re: Terminal Server for SBS 2003 License Problem
- Next by Date: Huge increase in outgoing traffic - how to figure out why?
- Previous by thread: Re: Terminal Server for SBS 2003 License Problem
- Next by thread: RE: Migration to SQL 2005 for Workgroups
- Index(es):
Relevant Pages
|
