Maybe I should expand a little. You can't be ignorant of technology, but you don't have to be able to write SQL queries to manage SQL Server DBAs.

You get explanations...

There are always little bugs and things that they include for tuning. I see a couple hot fixes a month, but most don't apply to me. However it would be...

Haven't tried, but if you post some DDL And code and explain where you're having issues, maybe we can help.

No logging for SELECTs, you are correct in that.

For the continuous selects, likely the data will remain in cache in memory, if it's the same or similar data, and you...

I'd also get rid of the t1.* and t2.*. If you're looking for matches, just get the PKs in the select list and then use that list to get the...

I'd recommend you try it with a regular login, maybe db_writer/reader in the db and see what happens. I've had a few of these applications "require" SA, but only one...

I wish. Unfortunately, too often people don't read the sticky things. I have to admit that on other sites I've missed them as well and restorted to asking an question...

Thanks and good post as well. And I hope your daughter is right.

Jereme,

Congrats!!!

If you don't have an idea of what is "normal" for your system, then there's no way of knowing if this is a good number or not. I wouldn't worry...

Has the server been rebooted?

I've used multiple NICs and IPs several times and it's worked fine. I don't think I've changed the server network utility, but can't remember.

I'm not sure a RAM disk is supported for Tempdb, but I know some people have done it. It should definitely help your queries since lots of temp operations in...

That isn't right. If anything, recreating indexes might cause more log space to be used.

Be sure the network people are backing up the log. Backing up the database is not...

Please double check that the job hasn't changed. You might not have changed something, but someone else might have. Also, check disk space and Mohammed's suggestions.

IS SQL Server not listening on this port, meaning you can't connect? Or does it now show in netstat?

If you haven't restarted SQL Server, it might not have picked up...