maximum degree of parallelism risks/caveats / sql server 2008

What are the risks/caveats of modifying the maximum degree of parallelism? We've just upgraded some hardware and there are some queries that actually got slower. I am thinking about setting the maximum degree of parallelism to 1 as this is an OLTP system. How impactful is it to toggle back-n-forth to view the impact? Please just consider the variables provided. Suggesting others is fine.

I'm hoping someone with experience with this provides some feedback.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

there are opinions on this topic here:

The majority of OLTP activity should fall under the 'cost threshold for parallelism'
which you can raise to force most activity below that.

Those that exceed that threshold might not really be classic OLTP (e.g. business intel) and parallelism may be appropriate - or those queries need rethinking/tuning.

reference in general:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.