Reputation
638
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
1 8 19
Newest
 Constituent
Impact
~42k people reached

  • 0 posts edited
  • 1 helpful flag
  • 56 votes cast
Aug
3
awarded  Constituent
Aug
3
awarded  Caucus
Jul
28
comment A query that lists all mapped users for a given login
I got stung with the same Collation problem due to Reporting Services Databases (Latin1_General_CI_AS vs Latin1_General_CI_AS_KS_WS)
Jul
25
awarded  Popular Question
Jul
22
accepted Create Linked Server to AlwaysOn Availability Group Listener
Jul
20
answered Create Linked Server to AlwaysOn Availability Group Listener
Jul
20
revised Create Linked Server to AlwaysOn Availability Group Listener
added 268 characters in body
Jul
20
asked Create Linked Server to AlwaysOn Availability Group Listener
Jul
16
awarded  Yearling
Jul
8
accepted Service Credentials to use in AlwaysOn Availability Groups?
Jul
8
comment Service Credentials to use in AlwaysOn Availability Groups?
@Kin Thanks. I was planning to use the group for that reason, just wanted to check if there was another less obvious (to me) reason.
Jul
8
comment Service Credentials to use in AlwaysOn Availability Groups?
Is the purpose of the DB1-SQL group so that you can assign the group permissions on all of the nodes? Or is there something extra I'm missing?
Jul
7
asked Service Credentials to use in AlwaysOn Availability Groups?
Jun
30
awarded  Good Question
Jun
18
accepted Should I use ReFS for a new SQL Server
Jun
18
comment Should I use ReFS for a new SQL Server
That's the question I'm asking - what scenarios (if any) should I use ReFS and when should I just stick to NTFS?
Jun
17
asked Should I use ReFS for a new SQL Server
Jun
12
accepted Manual Failover with AlwaysOn availability group
Jun
12
answered Manual Failover with AlwaysOn availability group
Apr
2
comment Can I install SQL Server Management Studio locally?
While I agree with your philosophy of SSMS >= the highest engine version you need to manage, we found that we couldn't edit a management package (don't hate me for it) on SQL2012 in SSMS 2014. It corrupted the file and SQL 2012 wasn't able to run it.