Viewing 15 posts - 2,701 through 2,715 (of 49,552 total)
Yup, frequently.
In full recovery model, index rebuilds are 'size of data' operations, which means that the entire thing gets logged. A rebuild of a 10GB index will require more than...
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
August 1, 2016 at 6:21 am
If there's no explicit transaction, then the locks are released at the end of each statement.
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
August 1, 2016 at 4:40 am
johnwalker10 (7/31/2016)
You can also take the help of these linkshttp://www.sqlrecoverysoftware.net/blog/sql-error-9003.html
http://sqltechtips.blogspot.com/2015/12/fix-error-9003-model-database.html
Both of those are horrible advice. (Emergency mode repair listed as the first option. Reinstall SQL?!?!)
This may sound blunt, but...
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
August 1, 2016 at 1:49 am
Eirikur Eiriksson (7/31/2016)
Quick question, did you take any kind of a backup before you started the repair exercise?😎
In this case no data would have been lost, the repair rebuilt the...
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
August 1, 2016 at 1:46 am
BigB (7/28/2016)
Just wondering why it is not updating tab1.id when select returning the result set. Anyway, how can this be achieved then?
Because there's no matching rows in tab1, so your...
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
August 1, 2016 at 1:35 am
Could well be, but many DMVs internally use OLEDB, so not definitive.
See if there's an updated driver and, if there is, try that?
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
July 31, 2016 at 3:44 pm
With Access Violations causing SQL to terminate, you may be best off opening a case with Microsoft's Customer Support if it's a repeated crash. CSS have tools to read through...
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
July 31, 2016 at 3:31 pm
If that number is for licensing purposes, then it's irrelevant how many SQL uses. You must license all cores visible to the OS.
You can't use SQL's processor affinity 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
July 31, 2016 at 3:29 pm
Mad-Dog (7/31/2016)
table scan is not good because some tables can have even millions rows for they temp table.
I didn't say it will cause table *scans*. Setting those options 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
July 31, 2016 at 10:55 am
Do the last 3 steps one at a time and see if the backup works after each one (after the copy, after the rebuild)
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
July 31, 2016 at 5:43 am
Mad-Dog (7/31/2016)
if i setup in the index page lock = false and row lock = false will it help reduce the locks on those tables?
Reduce the number, yes. Reduce the...
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
July 31, 2016 at 5:43 am
Not corrupt extent. Unallocated but unreadable page in an allocated extent (otherwise CheckDB would fall over it), and it's a guess.
Not easy at all to confirm, shrink may work, more...
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
July 30, 2016 at 2:41 pm
Shouldn't, but I've never replicated an AG DB before. Test it first.
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
July 30, 2016 at 1:03 pm
Could be it's in an unallocated page of an allocated extent (8 contiguous pages). CheckDB reads (afaik) allocated pages, backups copy out allocated extents
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
July 30, 2016 at 12:30 pm
Try publishing the DB. Create a single publication and drop it immediately, then remove replication from the DB again. May clean up the leftovers.
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
July 30, 2016 at 12:29 pm
Viewing 15 posts - 2,701 through 2,715 (of 49,552 total)