The approach we take at our workplace is that service accounts do not have password expiration in place unless we believe the account has been compromised.  The service accounts also...

What I would do is restore live to a dev environment.  Once things are on the development environment, run the stored procedure a few times as is so you can...

HAHAHA... that is the running gag in the office actually!  But the data in that database is critical to the company until the product goes EOL, yet it is running...

@ZZartin - that makes perfect sense.  I do agree that the "urgent" fixes can go live without prior approval or code review, but we DO still do a post-release code...

I do not have the actual numbers but the scenario was that an application (outside my department) was updated which took down production.  With production being down (the entire production...

I partially agree with you ZZartin.

I think there is no "one size fits all" solution, but I would also argue that with web-based content changes should be handled by the...

While I do agree that having the code go live quickly to fix a problem is nice, what if things go wrong?  What if that code release halts production and...

I am happy to help.  I do recommend you look into truth tables.  They can be very helpful when working with logic like this.  It is VERY easy to think...

Just saw your reply there skeleton567 and thought I'd reply too as our process has changed a bit as we changed managers.  Now, the process is still that it code...

Got an email from Degreed.com giving me recommendations for virtual training and … well, apparently there are urgent SQL courses I need to take today and ...

Well, what do...

The difference in how you create them, there is essentially none.  If you create a shared data source from the report builder window, it will create the exact same file...

I agree with Jeff here - you should be upgrading the SQL instance to something supported.  2012 is out of support.  I don't quite see this as going to spam,...

If you want to exclude, simply reverse your conditions.  For example, rather than "IN" use "NOT IN" or instead of "<" use ">=".  Or, alternately, toss some brackets around your...

I agree with Scott.  And to add to what he said - if you are currently using INT, I would MUCH rather switch to BIGINT before switching to CHAR(50).  I...

Where I work, the DBA patches the DBA software (SQL for example) and the IT team patches the OS.

So Windows updates are handled by IT and SQL patches are handled...