Technically speaking, If you managed to create a planet with an ideal gas atmosphere, the atmosphere would just float away. Why?

One of the approximations of an ideal gas is 


  
  There are no attractive or repulsive forces between the molecules or the surroundings
  


This means that the gas wouldn't feel the force of gravity!
So if I had a jar of ideal gas, the pressure wouldn't increase as I went to a greater depth in the jar(It does increase in gasses too, just like it does in liquids).

I know this sounds strange but all it really means is that you cannot apply the ideal gas approximation to a system the size of our atmosphere. This approximation works well for small systems(A jar of ideal gas), because the effects of gravity are pretty negligible.

So to analyse effects of change in temperature on the whole atmosphere, you'll need a better model. Maybe considering the atmosphere a non-viscous fluid can help, I don't know. You should research on this.

Note that other approximations like the Van der Waals equation wouldn't help too because they too neglect the effect of gravity.

Combined gas law in an open atmosphere
I've been working on code in T-SQL to add new schedules to a SQL Agent job  using the sp_add_jobschedule proc in the msdb database.  When I add a new schedule (typically a run-once at a specific date/time) and immediately look at the values in sysjobschedules and sysschedules, I can see that the new schedule has been added and is tied to the job_id for my SQL Agent job. However, the values for next_run_date and next_run_time have 0 in them.  When I come back and look at them again in 2 or 3 minutes, they still show 0's in them.  However when I come back another 5 or 10 minutes later, it now correctly shows the date and time values corresponding to the next scheduled run.

So my questions are:


How often do these values get updated?
What process is it that updates these values?
If I were to add a schedule that was, say, 1 minute in the future, does that mean that the job will not run since the next_run_date/time haven't been updated yet?


Example of the code I use to add a new schedule:

exec msdb.dbo.sp_add_jobschedule @job_id = @jobID
                    , @name = @JobName
                    , @enabled = 1
                    , @freq_type = 1
                    , @freq_interval = 0
                    , @freq_subday_type = 0
                    , @freq_subday_interval = 0
                    , @freq_relative_interval = 0
                    , @freq_recurrence_factor = 0
                    , @active_start_date = @ScheduleRunDate
                    , @active_end_date = 99991231
                    , @active_start_time = @ScheduleRunTime
                    , @active_end_time = 235959


where @jobID is binary(16) that holds the job_id of the job in question, @ScheduleRunDate and @ScheduleRunTime are INTs with the date and time respectively.
