I came close to that in CS3 and it worked OK. However, I find it easier to segment the project into smaller portions. For example, I might have a project for the intro, one for the first act (or in my case, the first day of the class), one for the second act and one for the third act. Then another for the summary, and one for the credits.
What this does is make it easier for me to find things, and it keeps the files smaller and easier to manage.
Once I have finished each section, I import all of the main sequences into one new project and put it all together for export.
Another way to do this is to bring it all into one project, and when working on a sequence, as it gets a decent rough cut, import it into a new project and finish it off there. Then you can import it back in all ready to go. That allows you to work with a bunch of smaller files and still have a huge file as the center of your workflow.
If you keep your project on a drive by itself, and make sure you have lots of room for auto-backups, you should be OK. As long as the program can save the file easily, without having to deal with fragmented drives, you should be OK. Using a SSD is not a horrible idea for a project of that size. Just make sure you clean off the old auto-backups now and then, and make sure you back up your SSD every day to an external drive. During the backup is a good time to think about deleting the prior day's backups. Or maybe a couple of days back.
Basically, i am just saying be careful and you will be OK.