Old Customizations

Thanks y'all.  I came into this role after it had been vacant for several months and I didn't find much documentation.  If a directory, repository, readme file were to exist, would it be saved in SSMS?

Thanks y'all.  I came into this role after it had been vacant for several months and I didn't find much documentation.  If a directory, repository, readme file were to exist, would it be saved in SSMS?

Kanani Reichlin said:

If a directory, repository, readme file were to exist, would it be saved in SSMS?

I was assuming a network location there. If I get hit by a bus, all of the files under "tessitura" in my home dir (or OneDrive these days) will contain everything anyone would want to know, and so much more... ;-)

As Chris said, likely not in SSMS (and, if you cannot find reference to one anywhere, unfortunately it probably does not exist).  Usually a repository is kept somewhere separate (e.g. bitbucket or AWS codecommit); that is where I keep all my code and readme files.

Chris Jensen said:

If I get hit by a bus

We don't get hit by buses, we win lotteries!  

I also (like Nicki) relabel, but with a 'z' in front so it drops to the bottom of lists.  I may change this up some day, but for now, and with so many other more urgent things to do, this is the easiest.  

I think you're right that it doesn't exist.  I looked through our old network location Tessitura folder and just found old copies of Tessitura provided documentation, stuff from when we were self hosted, and some bits and bobs of SQL from 2005-2008 (some written by Andrew Recinos himself! nifty!) I created a documentation team in 2020 but we've mostly focused on process documentation.  I need to wrap my brain around documenting the history of our entire database. Woof.

Setup and documentation layout would make a great community tips guide or webinar.

(or maybe I need to get Disney+)