How it got so big: You aren't running regular log backups. In full recovery model only log backups mark the log as reusable, so you need to schedule them. Full...

No point. In fact, unless losing 24 hours work off dev is unacceptable, there probably doesn't need to be diffs and logs, or maybe weekly fulls and daily diffs.

A full backup does not...

Full backups do not truncate the log.

If the database is in full recovery, you need to be running log backups. If you don't need point in time recovery, switch to...

prabhu.st (12/19/2013)

---

what I replied exactly to the Interviewer is, "Appending all the Columns into the INCLUDE option will not be a right decision, Instead, we can try tune up the...

Don't convert dates to strings for comparisons, just going to make a mess. Compare dates with dates, it's efficient and you're not going to run into problems with formats

Are you...

Don't. While it is possible to create...

jhaddow (12/19/2013)

---

After transferring the files to the new computer, the program worked fine for nearly a year. This was simply copying the .mdf and .ldf files that seem to...

SQL Server is not a file-based database. Moving the files isn't enough. Someone (preferably someone with a mediocre of SQL knowledge) needs to log into the SQL instance on the...

There's your problem right there. Identify most common queries, index to support them, have a good clustered index.

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

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

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

That's the less problematic part of it.

From books Online:

Missing and Double Reads Caused by Row Updates

Missing one or more rows that were not the target of update

When you are using...

So why do you use it if you don't know what it does?

Could you...

Could you post the execution plans please, not pictures of the plans?

Right click database -> tasks -> generate scripts.

Don't script the data, use import/export once you've created the database on SQL 2008.

Can't be done.

A SQL 2008 R2 database can only attach to SQL 2008 R2 or SQL 2012. SQL Server does not allow downgrading of database versions