If you want to remove all the data in the table, TRUNCATE TABLE.

Not necessarily. Simple may be fine if simple recovery meets the app's requirements for recoverability.

Each query has an associated cost which the query optimiser estimates for it. Upping the cost threshold changes the cost at which the optimiser will generate a parallel plan for...

The log file's there. Log backups can't be done which is why you cannot select any database which is in simple recovery model when the backup type is set to...

Am I slow today, or was this a little tricky to figure out? http://www.sqlservercentral.com/Forums/Topic1550137-1292-1.aspx

Ah, so it wasn't that the log file wasn't being displayed (which is what your previous posts stated), but that when the Backup Type options is switched Transaction log, the...

There's no where in the backup database task dialog where the log file is supposed to show up. Where in the dialog do you expect to see the log file...

Google "New features SQL Server 2014". 1st result: http://msdn.microsoft.com/en-us/library/bb500435%28v=sql.120%29.aspx

You don't have an issue.

The data volume is so low that the clustered index scan is the most efficient option. If the data volume grows to the point where the...

??

A transaction log backup doesn't need to know the location of the file, it's a backup via SQL Server.

What exactly are you trying to do and what are the exact...

Time to change ISP?

Probably because with only 3 rows in the table there's no point in doing anything else as the clustered index scan is the most efficient at that tiny data size.

and run a DBCC updateUsage to fix that negative free space.

You need two nonclustered indexes, one on each of the columns in the where clause.

What are the current indexes on that table?