Viewing 15 posts - 20,161 through 20,175 (of 49,552 total)
Personally I would strongly recommend that you remove that automated task entirely. Shrinking logs is not as harmful as shrinking data files, but it is still a poor thing to...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 22, 2012 at 1:39 am
How would you know/define whether the datatype is appropriate? Looping through the tables is easy.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 22, 2012 at 12:56 am
Don't shrink?
As I said, trying to shrink TempDB with the system in use is documented to be able to cause corruption, so it's really not a good idea.
Why is a...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 22, 2012 at 12:26 am
SELECT definition FROM sys.sql_modules AS sm WHERE object_id = OBJECT_ID('sp_upgraddiagrams')
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 3:49 pm
syscomments is deprecated, should not be used, only for backward compat with SQL 2000, use sys.sql_modules instead.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 3:44 pm
Corruption in the log is reasonably easy to fix, as long as it's the inactive portion. You've got backups right up to when this started?
Switch to simple recovery, run a...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 3:42 pm
Maybe. Depends how many rows will be affected, how many rows are in the table, how much concurrent access there is (and hence how much lock memory is available).
The updates...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 3:17 pm
Try using the sys.dm_sql_referenced_entities DMV.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 3:12 pm
Maybe worth a read: http://www.sqlservercentral.com/articles/Indexing/68439/
http://www.sqlservercentral.com/articles/Indexing/68563/
http://www.sqlservercentral.com/articles/Indexing/68636/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 2:29 pm
That's normal, expected, documented behaviour. SQL will take as much memory as it is allowed to, up to max server memory (plus a small amount of non-buffer memory)
p.s. If locked...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 2:26 pm
The clustered index key is present in all nonclustered indexes. That's one of the reasons that the clustered index is recommended to be on a non-changing column.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 2:23 pm
jason.nodarse (2/21/2012)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 2:22 pm
JeremyE (2/21/2012)
You can set the max server memory to 20 GB for SQL by executing the following:
EXEC sp_configure 'max server memory (MB)', '20480'GO
RECONFIGURE WITH OVERRIDE
GO
You don't need Override. Override is...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 2:20 pm
Lowell and Jeremy have both explained how to do it, one using the GUI, one using T-SQL.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 2:18 pm
phelmer (2/21/2012)
GilaMonster (2/17/2012)
Disabling it first means that the index is gone and not usable until the rebuild finished.
It also seems likely that you'd end...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 21, 2012 at 1:50 pm
Viewing 15 posts - 20,161 through 20,175 (of 49,552 total)