Opinions on version 9

[RRinTetons]

We're still on version 7 and quite happy, thank you, but it's going out of support in October, so we have to update to something. I've got a couple of contacts who've gone to version 8 and are happy; our VAR wants us to go to version 9. I like the idea of getting to the current version, but it seems like there are substantial changes in 9. So....

Anyone done an upgrade from 7 to 9? 8 to 9? How did it go? Smoothly? FRX issues, Integration Manager issues? SQL Server 2000 to SQL Server 2005 issues?

How about the user side? Did users easily absorb the changes? Was formal training necessary to make the change?

Anything else I should about before I barge ahead?

 

[jymm]

Ok - I made the leap earlier in the year (around March) and over all could not be happier

First I updated from SQL 2000 to 2005 - this was smooth as far as GP goes - only thing I would have done differently would be to move the GP database files to a seperate directory instead of letting them stay where 2000 (and 7) had them - ok, not my choice. Only issue we had was not involved with Dynamics (time card vendor's stuff did not like 2005 returning 'all that information')

Second I went from GP 8 to 9 & to FRx 6.5 - FRx was cake (for once) & GP only had the 'normal' problems with customized forms. I actually set up one of the main Dynamics companies on a test box and had users come in and do a few journals, SOP work, payroll... I think it helped that they all had newer versions of MS Office since the interface looked so similar. Only real issue I ran into was security. In V8 Dynamics gave you some nifty things called 'lists' for quick access to data - it is a freat time saver, but watch out - even though our manufacturing area had never even known that Payroll was on the system (and security WAS set up that way) the new 'lists' went around the security and VOILA - everyone could see the info. Took a bit to figre out which screens to turn off for which user groups. One of the things I REALLY like in V9 is the payroll updates & users being able to unlock themselves - these two things alone were worth the pain.

this help?

 

[barbola]

Your info helped me...but I wasn't the one asking. We are upgrading from 7.5 to 9.0 in a couple of months. We don't have a test server, so our vendor is setting one up for us - I have to send them our data and client folder. Then I will go there and run a test upgrade. The vendor will set us up with remote access to the test system so other users can test some transactions.

Do we really need to upgrade to SQL 2005?

I saw a demo of 9.0 and to me the only difference seemed to be the interface, and not the functionality. The reports still suck.

We don't have security turned on yet, that will be big if I can get that set up as well.

 

[barbola]

Your info helped me...but I wasn't the one asking. We are upgrading from 7.5 to 9.0 in a couple of months. We don't have a test server, so our vendor is setting one up for us - I have to send them our data and client folder. Then I will go there and run a test upgrade. The vendor will set us up with remote access to the test system so other users can test some transactions.

Do we really need to upgrade to SQL 2005?

I saw a demo of 9.0 and to me the only difference seemed to be the interface, and not the functionality. The reports still suck.

 

[jymm]

'the reports still suck' --- do't hold back Barb - tell us how you REALLY fell ...

I did not set up a test server in the true sense - I actually put SQL 2005 on my own box - installed Dynamics 9 there - and voila

I asked the same question a while back -

Wondered about speed of the conversion (it actually went pretty well here all things considered)

http://www.tek-tips.com/viewthread.cfm?qid=1189432

I noted that Integration Manager had problems, but got a hot fix from MS

http://www.tek-tips.com/viewthread.cfm?qid=1199229

and someone talked about which Dynamics versions went with which versions of SQL

http://www.tek-tips.com/viewthread.cfm?qid=1183125

anything else?

 

[jymm]

btw - SQL 2005 Reporting Services & Dynamics work REALLY well togeather - worth the leap just for those reports and giving some of the users access to reports and not have to give them Dynamics... worth it here.

 

[barbola]

I had problems submitting that and oops it's there twice.

I think I will see if our tech guy can upgrade to SQL2005. I really want the reporting services, and was mistakenly told by our VAR that SQL2000 has it. Uh..not the one we have.

Thanks for the heads up on IM as well.

 

[jymm]

Reporting services IS on sql 2000 - after seeing it in action on 2000 versus how it functions on 2005 - I like the design tools in studio better with 2005, but that is just me...

 

[jymm]

darn it - meant to include this link - watch/listen to the videos on the right to get you REALLY excited about it

http://www.microsoft.com/sql/technologies/reporting/default.mspx

 

[Borvik]

but it's going out of support in October

Really, I was under the impression from our var that it was happening in January see here.

If it really is October is there a link (so I can pressure my boss to allow the upgrade ).

 

[RRinTetons]

That's 7.5. We're still on 7.0, and that's the one I was told by our VAR is done in October. Other information suggests that it may already be out of support, but I can't find anything conclusive on MS's web site about that.

 

[Borvik]

Gotcha - I wasn't aware of the 7.0 version - oh well time to pressure anyway, thanks.

 

[barbola]

OK so how come I have SQL2000 but I don't have reporting services? How do I find it? where do i get it?

Our IT guy says we don't have it and we need some other thing...VB.net maybe? That makes no sense to me though.

 

[klewis10367]

I believe it is a seperate install than the SQl install. You should get it with your SQL License.

 

[RRinTetons]

re Reporting Services for SQL Server 2000 - it is a separate install. You're licensed for it as part of SQL Server 2000, but it doesn't install with the regular components. You can dl it from Microsoft's web site, though, and install it on your server. In order to author reports you'll need Visual Studio .NET 2003. If you're going to go to SQL Server 2005 you'll need Visual Studio 2005. The good news is that you can get one license for VS 2005 and a media kit for VS .NET 2003 and one for VS 2005 and the license is good for either.

VS 2005 is NOT cheap, and it's got a learning curve for folks who aren't programmers to start with, but it's a nice tool once you figure out how to use it. It's worth investing in some training if you want to get started quickly.

 

[barbola]

OK Thanks....Lucky Me..,The IT guy dropped off a nice green box on my desk last week...Visual Studio 2005. I get to install it myself on my workstation...

I am assuming I also need to install it on the SQL Server?

Cool posters! I'm debating whether to show off Mr Infinity and the Professor in my office, or put them in my son's bedroom!

Thanks,
barb