Viewing 15 posts - 7,171 through 7,185 (of 39,833 total)
Can we fix the known issues with SSMS? It's the only application out of hundreds...
February 3, 2017 at 7:14 am
February 3, 2017 at 7:13 am
I am in central Ohio,...
February 3, 2017 at 7:11 am
Good advice above. One note, don't be afraid of putting multiple columns in an index. If you tend to query by city and state and zip, put all those in...
February 2, 2017 at 9:42 am
February 2, 2017 at 9:38 am
Maybe database reporting specialist? Sounds more like what you do.
February 2, 2017 at 9:30 am
Jeff, that's just not true.
It was not a scripting issue. It was a connection issue. The user ran their purge commands against the live server, not the secondary server....
February 1, 2017 at 5:59 pm
February 1, 2017 at 4:36 pm
February 1, 2017 at 4:36 pm
Eric M Russell - Wednesday, February 1, 2017 8:35 AMEach Git user should still have their local commits.
Not necessarily if they...
February 1, 2017 at 4:34 pm
Bravery: https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-incident/
They had a live Google Doc open as they worked through the issues.
February 1, 2017 at 7:27 am
First, welcome and hope we can help.
Second, here's what I'd do. I'd make this a procedure, not a query. That way I can easily call it, stick it...
January 31, 2017 at 8:24 am
With SQL Server, DBA !(even close)= DBA. We all have such different jobs.
January 31, 2017 at 7:48 am
SQL Server 2016 is SQL 13 (RTM build 13.0.1601)
right now, SQL v.Next is build 14.0.200 (CTP).
SQL 15 will be SQL v.Next when there's a release next year. I'm...
January 30, 2017 at 2:30 pm
Viewing 15 posts - 7,171 through 7,185 (of 39,833 total)