After doing a search for the topic of "Source Control", I found quite a few answers that focused mostly on people who are developing exclusively for SQL Server and mostly using Visual Studio and Visual Source Safe to do the job.
However, my situation is a bit different: We have both an SQL Server environment, as well as an Oracle 11g environment, and have to build and maintain scripts for both.
Typically the development environment for each DB is left up to the individual user, due to how access is set up (our Oracle 11g environment is strictly read-only; the SQL Server environment is read-only for everyone but the three DBA users) - for example, I typically use Sublime Text 2 to do my coding, and then either use SSMS (SQL Server; obviously) or Toad Data Point or SQLTools (for Oracle) to actually execute and debug my code.
As a result, we've got a very large number of scripts that are pre-built and address most - but not all - of the reporting requests that my group gets. Many of them have been converted from Oracle to SQL Server and built into SSRS reports, and users can run them as needed on their own.
Others, due to either the complexity or in-frequency of requests or any number of reasons, just exist in a shared network location. Unfortunately this tends to lead to a lot of duplication of effort - or worse, a junior developer who fails to look closely enough, attempts to re-invent the wheel, and fails miserably, causing others even more work.
What we're looking for is some kind of source control system, preferably one that integrates at least somewhat easily with a Windows Network environment (Active Directory or at least the ability to control access based on NT ID), that has search capabilities, allows to assign permissions to edit or just read-only, etc. It needs to be platform independent when it comes to syntax, but if it uses a database backend, it would have to support SQL Server 2008 or 2008 R2.
Has anyone used a source control system in this type of situation? What did you use and did it work well?