You can have any schema you like, but whatever it is explicitly include it in front of all table references.
If you do
SQL will first look for the schema the currently connected session is using, and whether that has a Table or View, and when it doesn't find a MySessionSchema the Parser will then revert to "dbo"
So if you have either
the query parser will skip the step of looking for MySessionSchema.MyTable
All our stuff uses dbo - that's the default, and we've never fiddled with specific schemas.
We have a 3rd party APP where every table is part of a single TheAPP schema ... that just means that whenever we reference a table we have to include TheAPP, so it just becomes a PITA - they might as well have used "dbo.", so I suppose my answer would be:
If you only have one Schema in your DB / APP then easiest if you stick to "dbo."