Forum Replies Created

Viewing 15 posts - 2,521 through 2,535 (of 2,610 total)

  • RE: Version Control your Stored Procedures

    Grant Fritchey (5/7/2010)

    Also, we make it a point of retaining the scripts that were generated for the final rollout to production, in case there's any question in the future what...

    May 7, 2010 at 8:26 am

    #1164134

  • RE: Version Control your Stored Procedures

    bill page-320204 (5/6/2010)

    Am I missing something here?

    We use SourceSafe. We keep each proc separate. When I need to change one, I check it out, modify it, paste it...

    May 6, 2010 at 1:29 pm

    #1163565

  • RE: Version Control your Stored Procedures

    CirquedeSQLeil (5/6/2010)

    I would have like to see a more in-depth article on the facets of the scripts. I think this would have added more value to the article.

    I didn't...

    May 6, 2010 at 10:47 am

    #1163443

  • RE: Version Control your Stored Procedures

    bphipps-931675 (5/6/2010)

    But you lose the benefits of a change log that manual management of your procedures provides.

    In the version of the procedure I have adds and additional call to another...

    May 6, 2010 at 10:17 am

    #1163417

  • RE: Version Control your Stored Procedures

    bphipps-931675 (5/6/2010)

    True about the walking in late, for that issue but I would still want to logically arrange the various scripts into projects to make them easier to find and...

    May 6, 2010 at 9:42 am

    #1163377

  • RE: Version Control your Stored Procedures

    bphipps-931675 (5/6/2010)

    I guess this is where having a plan in place of how you are going to manage your scripts before you create 600 scripts is important.

    It is...

    May 6, 2010 at 9:21 am

    #1163342

  • RE: Version Control your Stored Procedures

    bphipps-931675 (5/6/2010)

    That's certainly one way you can get a script started if you didn't save it from the start. We have a stored procedure template (that we access via...

    May 6, 2010 at 9:14 am

    #1163336

  • RE: Version Control your Stored Procedures

    bphipps-931675 (5/6/2010)

    But SSMS inherently gives you a save option. All you have to do is save them like any other file to your hard drive. I really don't...

    May 6, 2010 at 8:51 am

    #1163291

  • RE: Version Control your Stored Procedures

    bphipps-931675 (5/6/2010)

    This just seems silly overall. Why wouldn't you just create a project in SSMS and then save your scripts into the solution/project. The solution can then be...

    May 6, 2010 at 8:35 am

    #1163264

  • RE: Version Control your Stored Procedures

    Phil Factor (5/6/2010)

    anything that involves a table schema change for example kind of makes the whole approach a bit complex and prone to problems

    Right on the nail. If you can...

    May 6, 2010 at 7:54 am

    #1163221

  • RE: Version Control your Stored Procedures

    mike.renwick-894639 (5/6/2010)

    I personally haven't found a great deal of info on how to script objects using SMO which is why I think people end up doing slightly scary things like...

    May 6, 2010 at 7:48 am

    #1163209

  • RE: Version Control your Stored Procedures

    mike.renwick-894639 (5/6/2010)

    I also had similar issues with sp_helptext and eventually found a way of scripting objects using

    Microsoft.SqlServer.Management.Smo.Scripter in Powershell.. this has the advantage that it handles all types of objects...

    May 6, 2010 at 7:46 am

    #1163208

  • RE: Version Control your Stored Procedures

    jcaradocdavies (5/6/2010)

    Just a small concern...

    As far as experience and memory serves, sp_helptext is not a reliable source for recreating SQL server objects. SQL management objects are the preferred source.

    Changes to...

    May 6, 2010 at 7:44 am

    #1163207

  • RE: Version Control your Stored Procedures

    irozenberg (5/6/2010)

    Just a small suggestion - please consider EXTENDED properties for DB objects (including Stored Procedures), by using them in a key-value fashion you could avoid a lot of text...

    May 6, 2010 at 7:41 am

    #1163206

  • RE: SQL Server 2005: Script all Indexes

    Dmitriy Burtsev (3/19/2010)

    FILLFACTOR is missing

    I've included code to include the FillFactor:

    --USE myDB

    GO

    IF NOT EXISTS(SELECT 1

    ...

    March 19, 2010 at 8:50 am

    #1136783

Viewing 15 posts - 2,521 through 2,535 (of 2,610 total)