Drawbacks to upgrading SQL after upgrading to PS2007?

[Angel]

We are evaluating the order in which to upgrade our EPM system and whether or
not we should push for the money to upgrade SQL before upgrading PS or if
that can legitimately wait.

Currently we are running PS 2003 and SQL 2000. Cost, as always, is a factor
and since SQL 2005 is not required in order to perform the upgrade, I'm
trying to find good reasons to present to management as to why we should
spend the money right now to upgrade to SQL 2005 prior to the PS 2007
upgrade.

I found a post that suggested doing the SQL upgrade first from a
troubleshooting perspective. But if I don't upgrade to SQL 2005 at the same
time as I upgrade to PS 2007, won't I know it's not a SQL issue since I
haven't changed anything in SQL? It seems to me it's just a matter or not
doing both at the same time. Is the process of upgrading SQL in PS 2007 any
harder than in PS 2003?

Any lessons learned or words of advice are greatly appreciated!

 

[Christophe Fiessinger [MSFT]]

Since PS 2007 has a lot more databases due to the SharePoint architecture
dependency I recommend the sql 2K5 ugrade before hand.
check this ppt: Understanding SQL Server Database Options for Microsoft
Office SharePoint Server 2007 on this blog
http://www.toddklindt.com/blog/default.aspx