Loads, no.

VLFs affect things which read the log. Restores, database recovery, that kind of thing.

The 10% growth is the problem here. You should have fixed intervals for growth, not %.

There's a reason Grant and I both recommend using traces or extended events....

The query which you decided to use instead only shows currently executing queries, which is near useless if...

http://www.sqlservercentral.com/articles/Indexing/68439/

http://www.sqlservercentral.com/articles/Indexing/68563/

http://www.sqlservercentral.com/articles/Indexing/68636/

All tables, almost without exception, should have a well-chosen clustered index.

http://www.sqlservercentral.com/articles/Indexing/68563/

Fair collection of questions. So what were your answers to them?

When you researched them after the interview, did you come up with anything that you're not sure you understand...

No.

No.

If it's not in the default trace, you haven't set up auditing and you aren't using source control, you cannot...

You can look in the default trace, but it only keeps a short amount of history, 5 files of 20MB. Other than that, unless you have some DDL auditing, no.

It's not...

HanShi (9/25/2014)

---

The only way to update multiple tables in a single statement is when you create a view over these tables and use the option WITH SCHEMABINDING. Then you are...

amns (9/25/2014)

---

Performance results for several options:

declare @int int = 123;

select column1,column2 from table where colInt = @int

(1 row(s) affected)

logical reads 7

SQL Server Execution Times:

CPU time =...

No!

Full backup does not clear...

SQLRNNR (9/24/2014)

---

And one more test for performance.

declare @string varchar(50) = 123;

select column1,column2 from table where colString = @string

This should cause an implicit conversion and wouldn't be far fetched when somebody...

If you're going to look at waits, you have to filter out the benign waits. All but one of the ones you've mentioned should be ignored. See Jonathan Keyhaius's blog...

Then you probably want to focus on tuning the procedure so that it doesn't need to...

This is a Microsoft SQL Server forum, we're not in general MySQL people here. Maybe try asking this over at http://forums.mysql.com/?