Cons. 1  Cannot span multiple databases... at least not easily. 2  All entities (tables, views, etc) need a primary key. 3  If you want to update a single column in a 100+ required columns table (not my table design), you have to pull down all 100 columns to make the update. Or use a Stored Procedure. I've had issues with some default values defined on SQL server not getting pulled into the entity model after a new record gets added. Usually this is with computed values, or values that get added in an INSERT Trigger On occasion, the SQL queries get badly written and are slow to execute.
Buying in advance is cheaper than buying at the station on the day and you could save an average of 43% on your train ticket. Advance tickets usually go on sale 12 weeks in advance, so the earlier you book the more likely you are to save.Ticket Alert.uying in advance is cheaper than buying at the station on the day and you could save an average of 43% on your train ticket. Advance tickets usually go on sale 12 weeks in advance, so the earlier you book the more likely you are to save. Ticket Alert.
In Europe. Once in Europe, you can simply get tickets at the station, usually without much fuss, either on your day of travel or in advance (see my tips for buying tickets in European train stations). This is the best option if youâd prefer to keep your itinerary more spontaneous.y buying through any US retailer, you may pay a little more than if you were to purchase that same ticket in person at a European train station â but for a canât-miss train, the extra cost can be worth it for the peace of mind.