Also if when you subtract your new Databases MaxPerm value from the Parent databases MAX Perm and you would go below Current perm of the Parent database you will get an error on the create Database.
The system will never allow your MAXPERM to go below Current Perm.
for example you have a database ( from exec showspace )
user MaxPerm CurrPerm
SysAdmin 40,000,000 23,815,104
Create database Sysadmin2 from Sysadmin as PERM= 17e6;
would give an error
The request to assign new PERMANENT space is invalid.
because you only have 16 Meg and change available to give away.
If you need to give more space away than you have between MaxPerm and Current Perm, you will have to delete some of your tables from that database to lower your current perm.
So in this case you would have to delete more than 815,104 bytes to get current perm below 23 Meg to allow you to give away 17 Meg of the 40 Meg allocation.
However if you issued
Create database Sysadmin2 from Sysadmin as PERM= 10e6;
It would work just fine and exec showspace would show
user MaxPerm CurrPerm
SysAdmin 30,000,000 23,815,104
SysAdmin2 10,000,000 0
That 10 Meg would be deducted from SysAdmin and given to SysAdmin2.
Conversely when you
Drop Database Sysadmin2;
That 10 Meg would go back to SysAdmin.
user MaxPerm CurrPerm
SysAdmin 40,000,000 23,815,104