Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Views on Private Messaging Expand / Collapse
Author
Message
Posted Tuesday, September 4, 2012 9:35 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, November 27, 2012 9:02 AM
Points: 114, Visits: 140
I've attempted to answer a newbie question recently and because some of their data is private, some of the thread happened in private messages - which may be confusing to anyone else following the thread.

Just wondered what any views, or consensus there is on private messaging

(And please No PMs on this subject)
Post #1354000
Posted Tuesday, September 4, 2012 9:38 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:24 AM
Points: 12,887, Visits: 31,835
t.brown 89142 (9/4/2012)
I've attempted to answer a newbie question recently and because some of their data is private, some of the thread happened in private messages - which may be confusing to anyone else following the thread.

Just wondered what any views, or consensus there is on private messaging

(And please No PMs on this subject)

I've not have anyone PM me sensitive data, but I do reply to them and tell them i will be posting in the original thread so others can benefit; I send them the answer as a PM, and also to the thread.

i guess if someone sent me a bunch of social security numbers or something sensitive, I'd tell them not to share sensiive data, and probably munge the data on their behalf when i posted it to the thread, since they didn't know better;
they'd learn from the post even better, i would reckon.


Lowell

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #1354003
Posted Friday, September 14, 2012 9:08 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 11:13 AM
Points: 15,527, Visits: 27,909
Yeah, if the question is a follow-up to a discussion in the thread, I tell them to post it to the thread and I answer it there. I won't mess up the conversation. If it's truly sensitive data (not one I've run into) I'm not sure what I'd do. I'm a little uncomfortable with private communication because it far too easily turns into free support, which ain't happening.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1359392
Posted Monday, October 1, 2012 2:02 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 6:12 PM
Points: 3,615, Visits: 5,229
Grant Fritchey (9/14/2012)
Yeah, if the question is a follow-up to a discussion in the thread, I tell them to post it to the thread and I answer it there. I won't mess up the conversation. If it's truly sensitive data (not one I've run into) I'm not sure what I'd do. I'm a little uncomfortable with private communication because it far too easily turns into free support, which ain't happening.


I've had a couple of people PM me when I was the only one who responded to their question. I also redirect them back to the thread. No sensitive data involved though.



My mantra: No loops! No CURSORs! No RBAR! Hoo-uh!

My thought question: Have you ever been told that your query runs too fast?

My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.


Need to UNPIVOT? Why not CROSS APPLY VALUES instead?
Since random numbers are too important to be left to chance, let's generate some!
Learn to understand recursive CTEs by example.
Splitting strings based on patterns can be fast!
Post #1366367
Posted Monday, October 1, 2012 2:08 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:58 PM
Points: 42,466, Visits: 35,532
If people PM me questions or followups to questions my only answer is 'please post this in the forums'.

As for private data, they shouldn't be sharing it at all. You haven't signed an NDA with that company, so they have no way of knowing that you won't go and sell that info or post it elsewhere.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1366376
Posted Monday, October 1, 2012 2:17 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, November 27, 2012 9:02 AM
Points: 114, Visits: 140

I couldn't glean any meaning out of the data at first - but now I realise it was stock price data! - probably way out of date now - But I've since deleted the PMs.



Post #1366383
Posted Monday, October 1, 2012 2:17 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 9:30 AM
Points: 2,422, Visits: 7,441
I've had a backup of a DB linked to me in a PM once or twice.

Same as Gail, I'll generally just tell them that questions should be posted in the thread so that everyone can benefit and to maximize the number of people likely to answer the question. When I've been given sensitive data, I reply that they should obfuscate any data that is posted online.



Not a DBA, just trying to learn

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better, quicker answers on SQL Server performance related questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/



If you litter your database queries with nolock query hints, are you aware of the side effects?
Try reading a few of these links...

(*) Missing rows with nolock
(*) Allocation order scans with nolock
(*) Consistency issues with nolock
(*) Transient Corruption Errors in SQL Server error log caused by nolock
(*) Dirty reads, read errors, reading rows twice and missing rows with nolock


LinkedIn | Blog coming soon (for sufficiently large values of "soon" )!
Post #1366384
Posted Monday, October 1, 2012 11:57 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 6:52 PM
Points: 36,773, Visits: 31,229
GilaMonster (10/1/2012)
If people PM me questions or followups to questions my only answer is 'please post this in the forums'.

As for private data, they shouldn't be sharing it at all. You haven't signed an NDA with that company, so they have no way of knowing that you won't go and sell that info or post it elsewhere.


+1000


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1366692
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse