|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Hello, is there any intelligent life at M$?the new Management Studio. So, far I'm not impressed, albeit, I will admit I have not spent that much time with it. One of the first tasks that I went to accomplish is to extract the DDL for some objects in one my databases. I see M$ has really screwed up this interface. When in SQL 2000 they have a radio button to select if you want a single file or each object its own file, I always pick the later. But in management studio I do not see that option, and it was not readily apparent how to do it. And here is a MAJOR GRIPE about M$. I don't think many of the arrogant developers or maybe its brain dead marketing maggots, or both, have ever worked in the real world. How hard is to add a filters to your tools? Even the old, but extremely useful Norton Commander could filter a directory list, but oh no this is beyond the ability of M$ to implement. And do they give you a filter capability when extracting the DDL -- NO!!! It makes it pain when you have 11000 stored procedures and over a thousand tables. We were very diligent to use naming conventions so it would be each to limit the list to something I interested in. And that does not even come close to biggest schema I have worked with (20000+ tables). Clue! What Clue? We're Microsoft we don't need clues we just want your money...all of it. noname wrote:
Show quote > I just installed the new MS SQL2005. I have been trying to get used to Hmmm isn't it less expensive compared to Oracle?> the new Management Studio. So, far I'm not impressed, albeit, I will > admit I have not spent that much time with it. One of the first tasks > that I went to accomplish is to extract the DDL for some objects in one > my databases. I see M$ has really screwed up this interface. When in SQL > 2000 they have a radio button to select if you want a single file or > each object its own file, I always pick the later. But in management > studio I do not see that option, and it was not readily apparent how to > do it. > > And here is a MAJOR GRIPE about M$. I don't think many of the arrogant > developers or maybe its brain dead marketing maggots, or both, have ever > worked in the real world. How hard is to add a filters to your tools? > Even the old, but extremely useful Norton Commander could filter a > directory list, but oh no this is beyond the ability of M$ to implement. > And do they give you a filter capability when extracting the DDL -- > NO!!! It makes it pain when you have 11000 stored procedures and over a > thousand tables. We were very diligent to use naming conventions so it > would be each to limit the list to something I interested in. And that > does not even come close to biggest schema I have worked with (20000+ > tables). > > > Clue! What Clue? We're Microsoft we don't need clues we just want your > money...all of it. Actually, they do give you the capability to extract DDL, based on name, via
SSMS. Using Object Explorer, drill down into your DB to, say, stored procedures. Right click on Stored Procedures->Filter->Fitter Settings. Here, you can filter on Schema, Name and Create Date. You then double click on Stored Procedures. They appear in the Summary pane, filtered. Select them all then right click them. Click on Script stored procedure as... -- Show quoteTom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA SQL Server MVP Columnist, SQL Server Professional Toronto, ON Canada t**@cips.ca www.pinpub.com <aquila.d***@gmail.com> wrote in message news:1133590884.814066.30730@g47g2000cwa.googlegroups.com... > noname wrote: >> I just installed the new MS SQL2005. I have been trying to get used to >> the new Management Studio. So, far I'm not impressed, albeit, I will >> admit I have not spent that much time with it. One of the first tasks >> that I went to accomplish is to extract the DDL for some objects in one >> my databases. I see M$ has really screwed up this interface. When in SQL >> 2000 they have a radio button to select if you want a single file or >> each object its own file, I always pick the later. But in management >> studio I do not see that option, and it was not readily apparent how to >> do it. >> >> And here is a MAJOR GRIPE about M$. I don't think many of the arrogant >> developers or maybe its brain dead marketing maggots, or both, have ever >> worked in the real world. How hard is to add a filters to your tools? >> Even the old, but extremely useful Norton Commander could filter a >> directory list, but oh no this is beyond the ability of M$ to implement. >> And do they give you a filter capability when extracting the DDL -- >> NO!!! It makes it pain when you have 11000 stored procedures and over a >> thousand tables. We were very diligent to use naming conventions so it >> would be each to limit the list to something I interested in. And that >> does not even come close to biggest schema I have worked with (20000+ >> tables). >> >> >> Clue! What Clue? We're Microsoft we don't need clues we just want your >> money...all of it. > > Hmmm isn't it less expensive compared to Oracle? > Yeah, I came into 2005 expecting to know it all, but the Interface is so
messed up, I gotta RTFM now too... or alteast unglue my F1 key... Show quote "Tom Moreau" wrote: > Actually, they do give you the capability to extract DDL, based on name, via > SSMS. Using Object Explorer, drill down into your DB to, say, stored > procedures. Right click on Stored Procedures->Filter->Fitter Settings. > Here, you can filter on Schema, Name and Create Date. You then double click > on Stored Procedures. They appear in the Summary pane, filtered. Select > them all then right click them. Click on Script stored procedure as... > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA > SQL Server MVP > Columnist, SQL Server Professional > Toronto, ON Canada t**@cips.ca > www.pinpub.com > > <aquila.d***@gmail.com> wrote in message > news:1133590884.814066.30730@g47g2000cwa.googlegroups.com... > > noname wrote: > >> I just installed the new MS SQL2005. I have been trying to get used to > >> the new Management Studio. So, far I'm not impressed, albeit, I will > >> admit I have not spent that much time with it. One of the first tasks > >> that I went to accomplish is to extract the DDL for some objects in one > >> my databases. I see M$ has really screwed up this interface. When in SQL > >> 2000 they have a radio button to select if you want a single file or > >> each object its own file, I always pick the later. But in management > >> studio I do not see that option, and it was not readily apparent how to > >> do it. > >> > >> And here is a MAJOR GRIPE about M$. I don't think many of the arrogant > >> developers or maybe its brain dead marketing maggots, or both, have ever > >> worked in the real world. How hard is to add a filters to your tools? > >> Even the old, but extremely useful Norton Commander could filter a > >> directory list, but oh no this is beyond the ability of M$ to implement. > >> And do they give you a filter capability when extracting the DDL -- > >> NO!!! It makes it pain when you have 11000 stored procedures and over a > >> thousand tables. We were very diligent to use naming conventions so it > >> would be each to limit the list to something I interested in. And that > >> does not even come close to biggest schema I have worked with (20000+ > >> tables). > >> > >> > >> Clue! What Clue? We're Microsoft we don't need clues we just want your > >> money...all of it. > > > > Hmmm isn't it less expensive compared to Oracle? > > > > > Daniel Regalia wrote:
> Yeah, I came into 2005 expecting to know it all, but the Interface is so I like having tabs but other than that feature everything I have tried > messed up, I gotta RTFM now too... > > or alteast unglue my F1 key... > is a pain Management Studio. From EM I expand to the Table right click and I have most of what I want to do right there including the query designer. I still have not figured out how to get it show up in Management Studio. Helps says in Mgt. Studio: 1. In Solution Explorer, expand the Queries folder. 2. Double-click the query you want to open. 3. Highlight the query statement(s), right-click the highlighted area and click Design Query in Editor. Does that mean I have to create a solution and/or project before using a query designer, @#$%&*? Give me a break. How stupid would that be! There is probably a way but it is sure not apparent to me. I tried the stupid process of first creating a project and doing what the three steps above said to do but at step three I don't see 'Design Query' as one of the choices. I went into to configuration and added it to the toolbar but it is always greyed out no matter what. noname wrote:
> Daniel Regalia wrote: Open SSMS. Click "New Query" on the toolbar. How hard can that be?> > Yeah, I came into 2005 expecting to know it all, but the Interface is so > > messed up, I gotta RTFM now too... > > > > or alteast unglue my F1 key... > > > I like having tabs but other than that feature everything I have tried > is a pain Management Studio. From EM I expand to the Table right click > and I have most of what I want to do right there including the query > designer. I still have not figured out how to get it show up in > Management Studio. > You want a GUI designer? Click Query / Design Query in Editor. I'd recommend you learn to write proper SQL the grown up way rather than mess with QBE grids - but that option still exists for those who need it. A lot of customer feedback went into SQL Server 2005. If you want to give your feedback for future versions you can email sqlw***@microsoft.com -- David Portas SQL Server MVP -- aquila.d***@gmail.com wrote:
> Hmmm isn't it less expensive compared to Oracle? Yes, Oracle is more expensive than SQL Server but SQL Server is way more > expensive than Postgres, :-). At the time the only database that could handle the load was Oracle. Believe me the company tried various hardware platforms with SQL Server to provide the same level of performance that Oracle/UNIX systems provided. They never were able to. |
|||||||||||||||||||||||