jwcolby
jwcolby at colbyconsulting.com
Thu Feb 9 12:08:28 CST 2012
I don't think I am missing the point. How can we use LS if LS itself is tied to an express instance on a specific machine? I understand perfectly that the app user data is not under discussion here. Why can't its internals be stored on a real server instance out on my server machine? Can you say "not ready for prime time"? Alternately, MS is aiming this at the "power user" only to be used on that one machine. Hmmmm sounds familiar.... Since the power user is building a little app for himself what does it matter if it can't be moved? John W. Colby Colby Consulting Reality is what refuses to go away when you do not believe in it On 2/9/2012 11:10 AM, Gustav Brock wrote: > Hi Arthur > > That is correct. > > What I tried to point out is the trouble carrying one version of an app and its local intrinsic data stored in SQLEXPRESS to another workstation and the local instance of SQLEXPRESS at that station. These data has nothing to do with the user data the app controls; these can be stored anywhere, including the local SQLEXPRESS. > > /gustav > > >>>> fuller.artful at gmail.com 09-02-2012 16:50>>> > I think perhaps the point is being missed here. AFAICT, LS uses Express for > its own purposes, and leaves you free to hook up the resulting app to a > real SQL Server just by changing the connection string. > > A. > > On Thu, Feb 9, 2012 at 10:18 AM, jwcolby<jwcolby at colbyconsulting.com>wrote: > >> And so... >> >> We wait for LightSwitch to grow up. ;) >> >> Obviously it is unusable (or barely usable) as you pointed out if it can't >> handle using a full SQL Server instance for its data store instead of >> requiring an Express instance. >> >> Perhaps when it grows up it will handle using a non-express instance? > > > _______________________________________________ > dba-VB mailing list > dba-VB at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-vb > http://www.databaseadvisors.com > >