Mike Stuart

Husband, dad, follower of Jesus Christ, SQL Server DBA, student of whatever strikes my fancy and just an all-around awesome guy. YMMV.

[Mike Stuart @mikethedba]

@sqlstudent144 I wrote a script around sp_DB/SrvPermissions to capture the output for auditing. Nothing special; just wondering if you'd like it to push out to the world? HMU @ [email protected]

[Mike Stuart @mikethedba]

@stridergdm @pshore73 @muad_dba @SQLTrooper When I left off on 12/23 the rollbacks were still going on. "Something" restarted SQL Server on 12/25 and the database recovered in 20-ish seconds. Who knows if the rollbacks finished before then or not? tl;dr - all is well. Thx for the help.

[Mike Stuart @mikethedba]

#sqlhelp Rolling back transactions that have been running between 6 and 19 DAYS. sp_whoisactive shows CPU use going up, transaction log size increasing... how so I know if the rollback really working? If not, then what do I do?

[Mike Stuart @mikethedba]

@SQLTrooper @muad_dba @tradney 2/2 As long as I'm seeing CPU increasing and file sizes staying sane, I'm thinking just let it ride. The spids had been running / blocked for over a week, so this won't be an easy or quick process, I'm afraid

[Mike Stuart @mikethedba]

@SQLTrooper @muad_dba @tradney Thanks Allen. As it turns out, the users won't be back on until Monday, so that gives a few days. I'm capturing database and tempdb file growth sizes, CPU activity and a few other parameters. 1/2

[Mike Stuart @mikethedba]

@muad_dba @pshore73 I'm in luck in that regard - there doesn't appear to be any other (non-system) processes running on the database, and I think the users are off until after New Year's

[Mike Stuart @mikethedba]

@muad_dba @pshore73 Would you ever recommend restarting SQL Server, vs. letting SQL-nature take it's course and continue rolling back? Is there's ever a case where restarting SQL Server is the right thing to do?

[Mike Stuart @mikethedba]

@SQLRockstar Thanks @SQLRockstar - same to you!

[Mike Stuart @mikethedba]

@pshore73 @muad_dba @pshore The one time I'm hoping for lengthy blocking - lol.

[Mike Stuart @mikethedba]

@muad_dba @tradney @muad_dba I did run KILL, and STATUSONLY doesn't return anything. No, this doesn't have anything to do with what you said - just some unknown, not-coded-for problem in the T-SQL that may or may not ever show up again. Thanks!

[Mike Stuart @mikethedba]

#sqlhelp: Creating script(s) to gather instance and database info in case of disaster. Any suggestions or recommendation? Already looking at the excellent @GlennAlanBerry collection!

[Mike Stuart @mikethedba]

Checked service manager, and "SQL Server VSS Writer" is showing up. Might this have something to do with the problem? Still, why is my brand-spanking new SQL 2014 installation pointing to (allegedly) non-SQL Server data files off in la-la-land? #sqlhelp

[Mike Stuart @mikethedba]

I did a SQL 2014 Express 32-bit install - failed with message: "Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes" #sqlhelp

[Mike Stuart @mikethedba]

Example: X:\sql12_main_t.obj.x86Release\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf #sqlhelp

[Mike Stuart @mikethedba]

1 - The errorlog is referring to files not even involved with SQL Server: "Unable to open the physical file <path>\<mdf_file>", where the path points to a network drive and path that have nothing to do with SQL Server?? #sqlhelp

[Mike Stuart @mikethedba]

@mrdenny TIA for your help! I did the install - they already have "SQL Server VSS" showing up in services. Install failed with that err msg. I checked in SQL Config mgr - no cert showed up, per your solution. SQL Server 2014 32-bit, due to software requirements

[Mike Stuart @mikethedba]

@mrdenny You say don't do it. I'm trying to install 2014 32 bit express and getting the error indicated. Why not?

[Mike Stuart @mikethedba]

@mrdenny Crap - nm. I just had to keep reading. Sorry Denny!

[Mike Stuart @mikethedba]

@mrdenny RE: this - https://t.co/L3wvOQkvR1

[Mike Stuart @mikethedba]

@trailsendsnacks Sent yesterday, no rply yet. [email protected] or 385-368-6831. Thanks.