Viewing 15 posts - 10,876 through 10,890 (of 49,566 total)
John Hanrahan (11/19/2013)
November 20, 2013 at 6:18 am
jcb (11/19/2013)
just for the record: avoid triggers, they are evil.
They are a tool. They can be used well or used badly. When used badly, blame the developer, not the tool.
November 20, 2013 at 6:15 am
Abu Dina (11/20/2013)
mote.ajit2 (11/20/2013)
Hi,But I have added one non clustered index column in select list. Now performance in significantly increased.
Perhaps an ORDER BY clause in your query is now using...
November 20, 2013 at 6:13 am
Ignore the 0. The database ID and object ID are what you need to identify the table that the blocking is on (and it is a table-level lock).
November 20, 2013 at 6:12 am
Please run a full CheckDB, not just a check table on the one table you know there's a problem with. I asked for a full CheckDB to see if there...
November 20, 2013 at 5:04 am
You can just add the new file (with a decent size) and disable autogrow on the first one. With an empty new file and an almost full existing one, SQL...
November 20, 2013 at 4:31 am
Please run the following and post the full and complete, unedited output
DBCC CheckDB (<Database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
November 20, 2013 at 3:21 am
Again, not enough information. Please read through the article I referenced.
If you create an index on a column that is just in the select clause, that index is probably useless.
November 20, 2013 at 2:25 am
No where near enough information to answer that.
Depends on the columns in the index, the where clause predicates, the selectivity of the index and more.
http://www.sqlservercentral.com/articles/Indexing/68439/
November 20, 2013 at 12:33 am
Database ID 15 (so the database with an ID of 15 in sys.databases)
Table ID 638292499 (so the table with an ID of 638292499 in sys.objects)
November 19, 2013 at 10:33 pm
Please don't cross post. It just wastes people's time and fragments replies.
No replies to this thread please. Direct replies to http://www.sqlservercentral.com/Forums/Topic1515848-1550-1.aspx
November 19, 2013 at 10:32 pm
A properly maintained log should not be growing.
Please read through this: http://www.sqlservercentral.com/articles/Administration/64582/
November 19, 2013 at 10:32 pm
Short answer - it doesn't. It forces the optimiser to use an index. It's possible that it will result in worse performance if the hinted index is not the best...
November 19, 2013 at 10:30 pm
Depends on your requirements and version. In SQL 2005, triggers are the main ones, on all tables with audit tables that they write into. On 2008 you also have Change...
November 19, 2013 at 11:28 am
Not unless you have some form of auditing or change tracking in place.
November 19, 2013 at 10:27 am
Viewing 15 posts - 10,876 through 10,890 (of 49,566 total)