SQL development in VS.NET

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is the SQL development environment that is provided in VS.NET supposed to replace the need for developers to use the SQL Enterprise Manager development environment or is it a limited but convenient environment. It is great that it is integrated with VSS but I don't see that it offers all of the tools of the Enterprise Manager so that I can work exclusively in VS.NET (eg. where is the SQL Profiler, DTS, etc.)?
 
Mike:
Mike Lane said:
Is the SQL development environment that is provided in VS.NET supposed to
Click to expand...
replace the need for developers to use the SQL Enterprise Manager
development environment or is it a limited but convenient environment. It
is great that it is integrated with VSS but I don't see that it offers all
of the tools of the Enterprise Manager so that I can work exclusively in
VS.NET (eg. where is the SQL Profiler, DTS, etc.)?
I believe its intent is to make things more convenient, but I don't think
it's intended to be a total replacement.. Depending on what type of
development you do and if your role is exclusively development vs some
administration, VS.NET isn't going to replace EM or QA. However, it does
obviate the need for a lot of clicking back and forth between apps. AFAIK
there is no way to run profiler, DTS etc directly from server explorer. If
you have a need to do everything from VS though, you may want to consider
writing some add-ins for your more common tasks.
 
Thanks for confirming that we (are development group) needs both environments. We would prefer to minimize the number of development environments used by individual developers and some here thought that VS.NET now could replace the need to use the SQL Enterprise Manger but it apparently isn't so (although it would be wonderfual if it were all available from one environment!)
 
Mike:
Mike Lane said:
Thanks for confirming that we (are development group) needs both
Click to expand...
environments. We would prefer to minimize the number of development
environments used by individual developers and some here thought that VS.NET
now could replace the need to use the SQL Enterprise Manger but it
apparently isn't so (although it would be wonderfual if it were all
available from one environment!).
There may be some other way, but I've looked into it and can't find it if
there is. Since EM is the UI tool for database administration and
development and administration are typically treated as seperate functions,
I can see why VS.NET wouldn't necessarily have all the features. I'll
double check it, but I've definitely tried to see if I coudl do it with VS
and always hit a dead end.

Bill
 
Back
Top