That's how we did it. From: [email protected] [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Wednesday, June 18, 2014 10:20 AM To: '[email protected]' Subject: [mssms] RE: SCUP install
I'm the only guy here doing patching, and we're just now looking into the 3rd party stuff, so I was only planning the one install. As long as the SQL CE and full blown SQL can co-exist, I'll just install it on my primary server. Thanks Jason! From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, June 18, 2014 8:11 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: SCUP install SQL CE and SQL Server are effectively two different things. SQL CE is a personal DB engine much like MS Access and will have no conflict whatsoever which an actual SQL installation. Remember also though that SQL CE is a personal DB engine and not really designed for shared use (once again, just like MS Access). While you can certainly share the DB file between multiple users (even though SCUP itself doesn't explicitly support this), there is no ability for concurrent use so plan accordingly. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Wednesday, June 18, 2014 9:49 AM To: '[email protected]' Subject: [mssms] SCUP install I'm looking at adding SCUP to my install, but not sure where to install it. I have one SCCM 2012 server at my location, with 14 secondaries throughout the state. However, the local install is using SQL already, so don't think that I should install SCUP on this box, since it uses SQL CE. How are you guys doing it? Joe
