WhiteLotus (1/20/2015)

---

Hallo All,

I have an issue in my production with long running query .. After analysing the index , I decided to add 1 non clustered index with 16 include...

robin.pryor (1/16/2015)

---

I have a server that is running out of space. I'm in the middle of correcting the problem, but error log files are generating at a staggering pace. Is...

Information about databases names and their options can be found in the sys.databases view.

select name from sys.databases.

From within a database context you can return data about the database objects from...

pvanhouse,

you need to do your shrink database with a notruncate option followed by truncateonly. The first option will move data at the end of the data file to unused,...

kramaswamy,

I would urge you to go to http://www.sqlskills.com and search "transaction logs" Anything you read there will help you but there are two specific articles by Kimberly...

Dastagiri16,

This is a database level setting and can be controlled at the level of an individual query as well. I do not believe there are any instance wide settings...

Ramana3327,

I would strongly encourage you to read Kimberly Tripp's articles on transaction log management. If you are going to be shrinking log files, it would be a good idea...

Aaitish,

I agree with previous person. If you look online for SHRINK Database and sp_MSForeachDB you should be able to put together a script that will loop through your database...

Peter2012,

I did a little research and came across a link to a Microsoft Support article that discusses how this error gets triggered. That led me to identify the two...

A repair operation got me going again.

We used backup exec and chose to back up with NTFS permissions. The other files we copied were from a machine also on SP1. Should we try replacing...

Windows is on the other drive array and was not touched.

Well the DB engine does not start so I don't know if the accounts and permissions restored. IT was the drive that had the ,mdf and .ldf files on...

Even though I set this up previously, the Log Reader Agent account was not set up in the Distribution database at all. That was my issue.

If your current job needs some SQL reporting done that is just not happening, then perhaps you can volunteer to create SQL reports to fill a business need you see....