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.
Making sure you have the right ticket is vital. Advance tickets can be cheap, but tie you to specific dates and times. Anytime tickets are the most flexible, allowing you to travel on any train at any time.e warned though, always check the terms and conditions of your ticket carefully before you commit to buy, as advance tickets restrict you to travelling on the train you book on so there's no room for last minute changes of plan. If you buy your ticket from a railway booking office, buy it during a quiet time of day.