As you mentioned in SQL Server 2000 the command to use is:
While in Enterprise Manager select the database you want to script objects from and then Right Click and select All Tasks -> Generate SQL Scripts...
While in the Options Pane it is handy to select option Create one file per object it that way you can store each object in source control separately.
So then whenever you do some updates on a tableA you can check it out in source control to let others know that you work on it and the after you finish you can script that single object and save check it in.
To script a single object you can you the same option All Tasks -> Generate SQL Scripts... and then select just that one object.
The only problem with that approach is when you want to restore the complete database you need to take care of dependent objects in the sense that the top level object must be restored before the ones dependent on them.
Ironically when you script the whole database to one file the objects are not ordered in terms of dependency but rather based on the creation date. That leads to errors when you try to use it to restore the complete DB.
We ended up creating batch file that would create each object separately calling "osql "
And that all worked pretty well at that time
Now we use SQLCompare Pro and it safes us from or that hassle, but if you do not make release frequently you can live without it.
