Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SamC
White Water Yakist
3467 Posts |
 Posted - 2007-05-23 : 09:51:33
|
| After moving production to 2005 mid-2006, which isn't too bad on the "learning new tricks" scale, I'm wondering if I'm missing something by not adopting SSMS projects as a mechanism of organizing stored procedures. You see, I still create my own folder structure and store all my SP's there. Report SPs, Admin SPs, Maintenance SPs, etc...I've cranked up a project folder, and I can't see any intuitive way of saving an existing SP there that brings any benefit beyond what I currently do. Navigate to a project folder, open it up, save the sp.Net benefit to an old dog: zeroI see articles on the net about add-ins to sort files in project. Seems like a headache is created by a project and add-ins are needed to solve the problem.I like my prior method of organizing SPs.Am I missing a key benefit of a project folder somewhere? Some magic that makes project folders worthwhile?Sam |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-05-23 : 10:31:24
|
| i haven't seen the "worthwhile" kick in yet..._______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenp |
 |
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2007-05-23 : 11:30:37
|
one possible benefit is that SSMS projects can integrate with a source control system. however I don't use it because projects in SSMS can't be organized into subfolders. a project is just a flat bucket of files, not enough for my needs.
www.elsasoft.org |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-05-23 : 13:22:39
|
| ... and SubVersion (say) can just handle a bunch of sub-folders as-is ... |
|
|
|
|
|
|
Old Dog Seeks New Tricks