|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Scripting options in new SSMSI am a little stunned by Microsoft removing the scripting options in the new
SSMS. All our teams developement is driven by scripting objects (view and procs) with the drop and create and including the permissions..... Not to mention the table indexes and primary keys.. How was something so basic omitted. Have they ever used SQL server in a remote server management enviroment where you test scripts on a ddev db and then deploy them to a live db by lookig at which scripts where changed last( hence the drop) I goes beyond understanding... (So now we are still stuck with QA and EM.. except we cannot use them on SQL 2005 databases) Productivity has gone backwards big time... Gerhard One thing I noticed was that if you right click on a database, you have the
option to "Generate Scripts" in the All Tasks menu item. This seems to have more flexibility/functionality than right clicking on a table (for example). -- Show quoteClint "Gerhard Pretorius" <gerh***@comprehendit.co.za> wrote in message news:ObmjWmA$FHA.912@TK2MSFTNGP11.phx.gbl... >I am a little stunned by Microsoft removing the scripting options in the >new SSMS. > All our teams developement is driven by scripting objects (view and procs) > with the drop and create and including the permissions..... > Not to mention the table indexes and primary keys.. > How was something so basic omitted. Have they ever used SQL server in a > remote server management enviroment where you test scripts on a ddev db > and then deploy them to a live db by lookig at which scripts where changed > last( hence the drop) > > I goes beyond understanding... (So now we are still stuck with QA and EM.. > except we cannot use them on SQL 2005 databases) > Productivity has gone backwards big time... > > Gerhard > Have a look at http://weblogs.sqlteam.com/billg/archive/2005/11/22/8414.aspx
-- Show quoteHTH Jasper Smith (SQL Server MVP) http://www.sqldbatips.com I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Gerhard Pretorius" <gerh***@comprehendit.co.za> wrote in message news:ObmjWmA$FHA.912@TK2MSFTNGP11.phx.gbl... >I am a little stunned by Microsoft removing the scripting options in the >new SSMS. > All our teams developement is driven by scripting objects (view and procs) > with the drop and create and including the permissions..... > Not to mention the table indexes and primary keys.. > How was something so basic omitted. Have they ever used SQL server in a > remote server management enviroment where you test scripts on a ddev db > and then deploy them to a live db by lookig at which scripts where changed > last( hence the drop) > > I goes beyond understanding... (So now we are still stuck with QA and EM.. > except we cannot use them on SQL 2005 databases) > Productivity has gone backwards big time... > > Gerhard > I don't think they intentionally left out the drops just to make your life
more difficult. Jasper has already pointed out a useful tool and I believe there are other 3rd party tools that do this and much more as well. But to the best of my knowledge the only thing missing is the ability to generate the drops in the same script as the creates. The ability to generate PK's are most definitely there. And you can actually generate the drops as a separate script just not together as most people want it. -- Show quoteAndrew J. Kelly SQL MVP "Gerhard Pretorius" <gerh***@comprehendit.co.za> wrote in message news:ObmjWmA$FHA.912@TK2MSFTNGP11.phx.gbl... >I am a little stunned by Microsoft removing the scripting options in the >new SSMS. > All our teams developement is driven by scripting objects (view and procs) > with the drop and create and including the permissions..... > Not to mention the table indexes and primary keys.. > How was something so basic omitted. Have they ever used SQL server in a > remote server management enviroment where you test scripts on a ddev db > and then deploy them to a live db by lookig at which scripts where changed > last( hence the drop) > > I goes beyond understanding... (So now we are still stuck with QA and EM.. > except we cannot use them on SQL 2005 databases) > Productivity has gone backwards big time... > > Gerhard > Thanks Andrew,
I agree, it was surely not intentionally, probably some kind of oversite. Althouhg I am all for the one interface (QA and EM combined) in SSMS and happy for new features to be introduced, it is just annoying when something so integral in your way of work just suddenly dissapears. It has been more than 8 years (including SQL 7 days) that we work with it. We call it the bits and pieces aproach, as we dod not use source control for sprocs and view scripts. The live database is where the "final" copy is, as that is the quality control. Also if there is a modified date on an object in the db we would not need to drop and create, because that date shows us what has changed. I see that this issues at http://lab.msdn.microsoft.com/productfeedback/ViewFeedback.aspx?FeedbackID=63dbc684-5f89-43db-a8a3-2548e008005e is apparntly the most voted issue on, so we hope MS will improve it. Gerhard Show quote "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:uM3bOiC$FHA.328@TK2MSFTNGP14.phx.gbl... >I don't think they intentionally left out the drops just to make your life >more difficult. Jasper has already pointed out a useful tool and I believe >there are other 3rd party tools that do this and much more as well. But to >the best of my knowledge the only thing missing is the ability to generate >the drops in the same script as the creates. The ability to generate PK's >are most definitely there. And you can actually generate the drops as a >separate script just not together as most people want it. > > -- > Andrew J. Kelly SQL MVP > > > "Gerhard Pretorius" <gerh***@comprehendit.co.za> wrote in message > news:ObmjWmA$FHA.912@TK2MSFTNGP11.phx.gbl... >>I am a little stunned by Microsoft removing the scripting options in the >>new SSMS. >> All our teams developement is driven by scripting objects (view and >> procs) with the drop and create and including the permissions..... >> Not to mention the table indexes and primary keys.. >> How was something so basic omitted. Have they ever used SQL server in a >> remote server management enviroment where you test scripts on a ddev db >> and then deploy them to a live db by lookig at which scripts where >> changed last( hence the drop) >> >> I goes beyond understanding... (So now we are still stuck with QA and >> EM.. except we cannot use them on SQL 2005 databases) >> Productivity has gone backwards big time... >> >> Gerhard >> > > Yes I am frustrated as well over the lack of some features that we enjoyed
before. From what you say you might benefit more from generating the scripts programmatically using SMO. You can automate the process and get more flexibility as well. -- Show quoteAndrew J. Kelly SQL MVP "Gerhard Pretorius" <gerh***@comprehendit.co.za> wrote in message news:OeEnhfI$FHA.3992@TK2MSFTNGP15.phx.gbl... > Thanks Andrew, > I agree, it was surely not intentionally, probably some kind of oversite. > Althouhg I am all for the one interface (QA and EM combined) in SSMS and > happy for new features to be introduced, it is just annoying when > something so integral in your way of work just suddenly dissapears. It has > been more than 8 years (including SQL 7 days) that we work with it. > We call it the bits and pieces aproach, as we dod not use source control > for sprocs and view scripts. The live database is where the "final" copy > is, as that is the quality control. Also if there is a modified date on an > object in the db we would not need to drop and create, because that date > shows us what has changed. > > I see that this issues at > http://lab.msdn.microsoft.com/productfeedback/ViewFeedback.aspx?FeedbackID=63dbc684-5f89-43db-a8a3-2548e008005e > is apparntly the most voted issue on, so we hope MS will improve it. > > Gerhard > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message > news:uM3bOiC$FHA.328@TK2MSFTNGP14.phx.gbl... >>I don't think they intentionally left out the drops just to make your life >>more difficult. Jasper has already pointed out a useful tool and I >>believe there are other 3rd party tools that do this and much more as >>well. But to the best of my knowledge the only thing missing is the >>ability to generate the drops in the same script as the creates. The >>ability to generate PK's are most definitely there. And you can actually >>generate the drops as a separate script just not together as most people >>want it. >> >> -- >> Andrew J. Kelly SQL MVP >> >> >> "Gerhard Pretorius" <gerh***@comprehendit.co.za> wrote in message >> news:ObmjWmA$FHA.912@TK2MSFTNGP11.phx.gbl... >>>I am a little stunned by Microsoft removing the scripting options in the >>>new SSMS. >>> All our teams developement is driven by scripting objects (view and >>> procs) with the drop and create and including the permissions..... >>> Not to mention the table indexes and primary keys.. >>> How was something so basic omitted. Have they ever used SQL server in a >>> remote server management enviroment where you test scripts on a ddev db >>> and then deploy them to a live db by lookig at which scripts where >>> changed last( hence the drop) >>> >>> I goes beyond understanding... (So now we are still stuck with QA and >>> EM.. except we cannot use them on SQL 2005 databases) >>> Productivity has gone backwards big time... >>> >>> Gerhard >>> >> >> > > And correct me if I'm wrong but you also no longer have the ability to
script just user permissions. You get CREATE or DROP but if you want a script of /just/ the permissions you're out of luck. FRUSTRATING... Andrew J. Kelly wrote: Show quote > Yes I am frustrated as well over the lack of some features that we enjoyed > before. From what you say you might benefit more from generating the > scripts programmatically using SMO. You can automate the process and get > more flexibility as well. >  |
|||||||||||||||||||||||
Other interesting topics