using SQL Server 2005 and VS 2003? Are they "ready for prime time?"
Thanks,
TWhat functionality you want to use in SQL 2005? Maybe MSDE will be a better
choice?
Sql Server 2005 is not a very good DB to use for production apps because it
is still beta and noone can guarantee that feautures you are using not
change in the release. My opinion is to wait for release before going to
production.
Gaidar
"Tina" <tinamseaburn@.removespamexcite.com> wrote in message
news:ucy1aYLWFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Is it safe and productive now for production applications to be developed
> using SQL Server 2005 and VS 2003? Are they "ready for prime time?"
> Thanks,
> T
It is never safe to put a beta product in production status! No matter how
good the new product is !
John
"Tina" <tinamseaburn@.removespamexcite.com> wrote in message
news:ucy1aYLWFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Is it safe and productive now for production applications to be developed
> using SQL Server 2005 and VS 2003? Are they "ready for prime time?"
> Thanks,
> T
I think you'd be running quite a risk. What if someone published a security
exploit? With beta code, Microsoft would be in no hurry to issue a patch.
The "fix" advice could be to stop using the beta until the next beta release
or the RTM version.
"Tina" <tinamseaburn@.removespamexcite.com> wrote in message
news:ucy1aYLWFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Is it safe and productive now for production applications to be developed
> using SQL Server 2005 and VS 2003? Are they "ready for prime time?"
> Thanks,
> T
Another danger is that you couldn't move your data from the beta to the
release version because of an incompatibility/bug.
"Tina" <tinamseaburn@.removespamexcite.com> wrote in message
news:ucy1aYLWFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Is it safe and productive now for production applications to be developed
> using SQL Server 2005 and VS 2003? Are they "ready for prime time?"
> Thanks,
> T
0 comments:
Post a Comment