I'm writing a recommendation for an upgrade scenario from SharePoint 2007 to SP2010.
Customer is currently running x64 SQL Server 2005 SP3 on Windows 2003 Server.
Does anyone have pros/cons for upgrading to 2008 server?
From what I saw in benchmarks, it's not a huge performance gain to upgrade to SQL 2008.
Any insight will be appreciated :-)
From what i have read so far, i am aware that SQL Server will need to be 64-bit and at least SQL Server 2005 SP3 Cumulative Update 3 to run SP2010.
I'd add to Wictor's items:
Anders, slightly off topic for your SQL question, but I put some stuff down in a blog post regarding the upgrade path for SP2010, it might be useful for your recommendation. Then again it might not be, but its there if you want to take a look.
Take a look at this article for lots of reasons to use SQL 2008 http://blogs.msdn.com/bobgerman/archive/2009/04/07/moss-2007-and-sql-server-2008-better-together.aspx
I want to create a new SharePoint 2010 farm using PowerShell. I use the following command: New-SPConfigurationDatabase When issuing this command (and providing the needed parameters) I get the following error: New-SPConfigurationDatabase : This SharePoint farm currently has pending upgrades. The cmdlet New-SPConfigurationDatabase cannot be executed until the upgrade is completed. When running the "SharePoint 2010 Products Configuration Wizard" I'm able to create a farm. I have a freshly installed Windows Server 2008 R2 with SQL 2008 R2 on the same box (it's a demo box
I am currently trying to upgrade my two WFEs from 32 bit Windows Server 2003 to 64 bit Windows Server 2008. I also have a 64 bit Windows server 2008 in the farm as an index server, and a 64 bit SQL 2005 box running Windows server 2008. I am using kerberos authentication to allow for smart card auth on the ISA 2006 server. After upgrading one of the front ends I am unable to access it through ISA. I get the multiple prompts even though I am entering valid credentials. When looking in the sever logs there are numerous kerberos errors referencing a null sid. Does anyone else have
We have recently migrated our MOSS databases from MS SQL Express 2005 to MS SQL 2008 both intances running on the same Windows 2003 server. After "successful" migration we switched the 2005 server... on the aevent viewer saying that couldn't find SERVER\SQL2005\MOSS_ConfigDatabase so we swtiched back on and start to research about what could the problem be? After few hours of research we found out that it seems that all the timer-jobs are executed from the old database on MS SQL 2005. So we went in to the config database and we realize that the table TimerRunningJobs on the 2008 config database
On a single Windows 2008 Server I'm running SharePoint 2007 Enterprise (SP2, December 2009 CU) and SQL Server 2005 (SP3, CU 7). Authentication is NTLM. I've been trying to get SharePoint Reporting... to the computer cannot be established'. There is no error logged to the ULS logs or the Reporting Services logs about this. I've tried: a complete uninstall and reinstall both SQL Server and SharePoint (as it is impossible to only uninstall the Reporting Services component with SQL Server 2005) used the same service account for all SQL services and the same for all SharePoint services given all
I have a two machine set-up, with MOSS 2007 installed on one server (Machine A), and SQL Server 2008 installed on the other (Machine B). In order to run SS Reporting Services in SharePoint integration mode on Machine B, I've read that I need to perform a minimal install of SharePoint on Machine B, and am wondering why. From a couple of error messages I see that it seems like Reporting Services in integration mode makes use of the SharePoint Object Model, but I haven't explored any further. So, purely just out of interest, why is it that I need to have a minimal SP install if my report
What could that message stem from? Any quick tips to diagnose? Single server farm, remote SQL. IT guys in another location, I have no VPN for access to SCAW (Central Administration Web) .
without any particular rights: SPF_DATABASE for database credentials SPF_ADMIN for farm credentials Added domain administrator in SQL Server 2008 R2 with sysadmin rights started Sharepoint Powershell as domain administrator (so I have rights to access domain accounts) I didn't install SQL Server 2008 KB 970315 x64, because I'm running R2 version - as I understand this is SQL Server 2008 SP2...I'd really like to prepare development environment for Sharepoint 2010. This is what I did: I installed Windows 7 x64 I installed VMWare Workstation Created a VM domain controller based on Windows
I keep getting a large number of the following warnings in my SharePoint Farm. Event Type: Warning Event Source: Office SharePoint Server Event Category: Workflow Features Event ID: 7397 Date: 1/31/2010 Time: 1:22:21 PM User: N/A Computer: MOB-INTRA-APP2 Description: message For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I am using Windows 2003 R2/ MOSS 2007 + SP1 / SQL 2005. This warning is being repeated too many times in the event log. Any idea what this warning might be about?
While accessing My Site -> My Interests and Newsfeed Settings, I am getting this error: Error An unexpected error has occurred. Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: ee7ff5fe-feed-472e-add8-639424410447 Date and Time: 4/8/2010 2:23:31 PM However the My Site -> My Colleagues option work well. Anybody faced this problem before? Environment: SP2010 Server on Windows 2008. I am using Administrator ID to login to the site. Digged the LOGs and found this: 04/08/2010 14:33:14.55 w3wp.exe (0x0828) 0x1AFC SharePoint