>>>>In the first case, create database diagram also as part of the documentation of proposed database. In the second case, you can also use DB diagram, but will need to select just newly created objects.
>>>
>>>I don't understand about "separate database". You mean to create a database just for documentation?
>>
>>No, I mean, do you need a separate database for your application or you're adding tables/indexes to some existing database?
>
>This is work in progress. I have one database (in SQL Server) which is a "copy" of the VFP database. And I am making all kind of changes to this SQL Server database (adding indexes, constraints, etc). And the application will use this one database. Does it make sense?

Yes. As part of the documentation process you can use Database Diagram. There are other tools available on the market for a good documentation, say, we're using RedGate (but not exactly sure which product) to create a nice Help file.