Hello,

We are currently in the process of migrating to MCMS2002. What is the best
practice to set up the SQL database for a shared development environment? We
have consultants who are suggesting to put SQL server on each developer's
machine and then have the developers sync up with the central SQL server by
means of running SDO extracted from central SQL periodically. I am leaning
towards following Microsoft's guide, i.e. install a central development SQL
server period and have every single development machine points to the same
database on that server.

I can see a point that raised by the consultants that the placeholder
definition is stored in SQL and cannot be rollback if change is made on a
central SQL server setup. On the other hand, I see immediate problems with
trying to synchronize all the SQL servers on different machines.

Any suggestions?

thanks.

[ Post a follow-up to this message ]

Setting Up a Shared Development Environment in MCMS 2002
http://msdn.microsoft.com/library/d...haredDevEnv.asp

/Mark H



"cgi1" wrote:

> Hello,
>
> We are currently in the process of migrating to MCMS2002. What is the best
> practice to set up the SQL database for a shared development environment? 
We
> have consultants who are suggesting to put SQL server on each developer's
> machine and then have the developers sync up with the central SQL server b
y
> means of running SDO extracted from central SQL periodically. I am leaning
> towards following Microsoft's guide, i.e. install a central development SQ
L
> server period and have every single development machine points to the same
> database on that server.
>
> I can see a point that raised by the consultants that the placeholder
> definition is stored in SQL and cannot be rollback if change is made on a
> central SQL server setup. On the other hand, I see immediate problems with
> trying to synchronize all the SQL servers on different machines.
>
> Any suggestions?
>
> thanks.

[ Post a follow-up to this message ]

Hi Mark,

That's the one I'm leaning towards to use. However I need to have a better
reasoning to counter the consultants' opinion (which they said worked nicely
on their previous engagement).
Any issue that might come up using a single central SQL database for all
developers? (Beside changes to placeholder definition can't be rolled back)

thanks.

"MarkH" wrote:
[vbcol=seagreen]
> Setting Up a Shared Development Environment in MCMS 2002
> http://msdn.microsoft.com/library/d...haredDevEnv.asp
>
> /Mark H
>
>
>
> "cgi1" wrote:
> 

[ Post a follow-up to this message ]

My developers each have an instance of Virtual Server 2005 with Windows
Server 2003 and SQL Server 2000 that they develop against. Periodically we
migrate .SDOs to our Beta environment manually via the site manager but only
for template changes. Each developer has a MSDN Universal Subscription so we
where able to achieve this setup for the cost of the subscriptions only.

>MH

"cgi1" wrote:
[vbcol=seagreen]
> Hi Mark,
>
> That's the one I'm leaning towards to use. However I need to have a better
> reasoning to counter the consultants' opinion (which they said worked nice
ly
> on their previous engagement).
> Any issue that might come up using a single central SQL database for all
> developers? (Beside changes to placeholder definition can't be rolled back
)
>
> thanks.
>
> "MarkH" wrote:
> 

[ Post a follow-up to this message ]

I have had good experiences with a central SQL server for multiple
developers, all using Virtual PC with Win2K3, MCMS and VS.NET.  I have
also set up, on the SQL server, a second database and instance of MCMS
- so the SQL server is ultimatly both an SQL server and an MCMS
instance.  Tie the MCMS instance on the SQL server to the second
database so you can create an integration environment.  Once developers
are done with their code, they can migrate the template files to the
SQL server and import the SDO from the development database to the
integration database for further testing.

Shawn

cgi1 wrote:
> Hello,
>
> We are currently in the process of migrating to MCMS2002. What is the best
> practice to set up the SQL database for a shared development environment? 
We
> have consultants who are suggesting to put SQL server on each developer's
> machine and then have the developers sync up with the central SQL server b
y
> means of running SDO extracted from central SQL periodically. I am leaning
> towards following Microsoft's guide, i.e. install a central development SQ
L
> server period and have every single development machine points to the same
> database on that server.
>
> I can see a point that raised by the consultants that the placeholder
> definition is stored in SQL and cannot be rollback if change is made on a
> central SQL server setup. On the other hand, I see immediate problems with
> trying to synchronize all the SQL servers on different machines.
>
> Any suggestions?
>
> thanks.

[ Post a follow-up to this message ]