It's not really that long of a story. This is a homework problem you're asking us to help you solve. Northern Virginia Community College ITN 170. coursehero.com/file/13907290/passwdadded Please be slightly more honest when you're asking the questions. — John Deters4 hours ago
@AndriyM @ypercubeᵀᴹ @dezso Kinda relying on you guys to indicate which comments are obsolete there and to add an answer at some point if possible. Cheers.
I'm kinda curious myself to understand what the reason for the slowdown is. Increasing versions of changed rows?
@TomV You can accept your meta answer now.
It's not a real database. We should close those questions and send them to Super User. — Evan Carroll3 hours ago
What's the process of migrating a question from SO here, we flag it and then the ops at StackOverflow ignore the flags because they thing everything is on topic there?
What's the future of this community when all the branding is behind StackOverflow and nothing gets migrated because their domain was never narrowed when new community sites sprung up?
If you were to tag-query all of the sure fire database-only questions on StackOverflow, you would find that StackOverflow saturates the database questions targeted to the platform. That should be an indicator of a huge problem.
If I look at [postgresql] there were more questions in the past 4 hours than dba.SE got all day on PostgreSQL. So not just is this more niche, but it has less traffic and it's probably growing at a smaller rate and just dividing expertise within the SE network.
@EvanCarroll If you see a particular question that belongs here, feel free to one-box into this chat room and explain its merits. A number of the regulars here have VtC on SO.
I was just about to ask a database related question (involving translations between SQL and MySQL) when I remembered that there's a whole site in the Stack Exchange network dedicated to databases!
But then I thought to myself, "Hmm... Which site should I put my database question on?"
So I check...
Oh, I have VtC close too. That's just half the issue. I'm not sure how many VtC's you need to get the migration. I've been using my 50 a day.
The big problem is the one the SE is totally ignoring and not failing to address. It should be addressed programatically and with a change in social policy as new sites move out of beta and chip away from the trilogy.
For instance, if your only tag is postgresql that question shouldn't even be allowed on StackOverflow. It should automatically be migrated or the user should be pointed to dba.se.
That's a big question. See the meta.SO Q & A above for some recent-ish changes in emphasis on their side (it seems to me anyway).
I don't personally have a huge problem with the current arrangement. Database questions can be on-topic in both places (but only one at a time!) There are different audiences, so answers are quite likely to be from different perspectives at least. I'm pretty sure the community here is not in favour of a sudden huge increase in volume and presumed lowering of average question quality.
This is a pretty straightforward meta question (I hope).
Why are there so many database questions in StackOverflow and when should they be posted here instead? What is the criteria for when it goes on SO vs DBA?
There is no way you can maintain a position that only encourages questions that are specialized enough so as if to exclude junior level and entry-level questions on enterprise products.
"By 'database professional' there, I mean someone whose work and experience is specialized to one or more database or database-related products." That's quite elitist and hardly how you grow a community. Under that plank the community will struggle to reproduce itself. People will make SO their one stop shop and never grow up.
It begs the question, rather than addressing it. That question being, when does the submission demand a different forum. It implies that someone who isn't a database professional that's learning the craft will one day feel confident enough to move to a different forum while they still have questions. But developing from an amateur to a professional isn't like that. It's a continuum of growth on a slope, not a jot down the street and a jump to a new height.
I would say a beginner can be a database professional if that's the primary focus of their activity. It's tough to get the wording right for everyone. Certainly not intended to be elitist or exclusive, just defining one of the main differences I perceive between dba and SO.
The original proposal for dba was quite clear on the "expert-level questions" thing . I'm not sure we all still feel that way. We do debate it from time to time on meta. It would be a big shift, though some would argue good basic questions are already often de facto on topic since they are answered and not closed/migrated.
But, that's a bizarre difference and it's elitist. You view SO as being questions that are simply less skilled and demanding about databases. SO is a professional site in and of itself. There are programmers that can read the code of PostgreSQL and are likely better than lot of database administrators here that can hardly rtfm.
The easier and more professional distinction would be to separate the domain on the question and not the skill level of whomever asked it. If the question doesn't involve programming in some non-sql language or a libraries or api, then it's certainly off-topic for S…
@EvanCarroll Having a growing community isn't a goal in itself. The goal is collecting answers to common, and perhaps not so common, questions in a specific knowledge domain. A community, growing or not, is just a means of achieving the goal. If it so happens that the community needs to grow to process the incoming flood of questions bringing them, as well as the answers to them, to an established format and level of quality, so be it. The growth shouldn't harm the ultimate goal.
@EvanCarroll That may be what you (or some askers) consider the goal, but writing someone else's code in my spare time is not something I particularly enjoy
But answering their high level questions when you're a skilled professional in the field who gets paid in that very line of work -- that's what you like to do in your free time? If it's about the stature of being a highly skilled professional tackling hard questions consider giving your clients a 100% discount.
In my case I like to provide longer answers that could possibly help future googlers learn, just as I benefited a lot in the past from finding other peoples posts hopefully contributing to the quality of the community and development as a whole
Solving very localized questions only helps the OP and nobody else
Because this is probably my first month being active on DBA.SO, and I'm in your top 3% this month which tells you just how dead and unhealthy this community is. Not to mention despite your rhetoric about skill, the questions are easy as piss here compared to the questions on SO. And, part of the reason is because they care about the community and not just end product.
They cater to the community so well, people don't want to leave when their question hits a certain threshold just so they can join the elitist kids.
For example one of the things I like to do is change a title so it caters better to google searches and edit the question/answer so it's more readable and more useful to future searchers
that doesn't get me a single unicorn point, and I edit a lot more than I answer
Well that's easy.. Most of it is because you don't have many questions on this site. Most of that is because the community that asks the questions are both legitimately confused as to where they should direct them, and more welcomed in the other non-elitist forum. I'm trying to solve those problems and I'm getting lots of excrement about how the other questions are too simple, how they're just for exp, and how people should only come here if they're super l33t h4x0r consultants.
So I'm challenging the elitist notion and arguing the best method to define the site is by content, and not the professional status of the questioner. That way this doesn't just become a circle jerk of elitists.
So in practice, what I would say is that if a question is tagged with postgresql and nothing else (or god forbid, even sql-server) that the question be deemed off limits for Stack Overflow, and suitable for this site.
If we accepted and advocated for that position with SO, we could expect (a) more questions, (b) more awareness of DBA.se, (c) a site with a less subjective and in-the-eyes-of-experts distinction.
I think mentioning the professional status in the site description has to do with the primary target audience, as well as with the desired tone or level of quality of the questions and answers.
@AndriyM which would be fine but that is being used to defend the status quo of Stack Overflow.
And the status quo of Stack Overflow is to not-close questions that fit their community's definition which does not currently exclude database-questions because they perceive that this site is not created for questions that are explicitly database-oriented, but only questions that require unique and specialized skill which also isn't off topic there because SO is a site for professionals.
@EvanCarroll I don't see a problem with some database-related questions being on-topic on both sites. I wholeheartedly agree with the points in Paul's meta answer. I don't believe the fact that a question is about SQL, alone, should define where the question belongs.
Right, and that's why Stack Overflow has more questions about the database, more questions about sql, and because of the community, more specialized questions about both. Also why I'm here in the top 3% this month and the site is dragging along as a club for elitists rather than an asset that could benefit a great amount of people.
Besides, why should it look as though we are competing against SO in who gets more database-related questions? Google makes them equally accessible to anyone.
I'm getting out of this non argument, it could be had in the superuser or security chat room because they should compete with serverfault, or in the programmers chat room how they should compete with SO or whatever
there is some overlap in the questions, there is some overlap in the answerers, there is a different perspective
You've got the status-quo (which has evident and clear problems), and a fall-back to a totally inane claim to perspective/audience/(next novel term introduced that means the same thing).
@EvanCarroll None of that looks to me like a benefit in itself. What's the point of having a ton of rubbish questions only because they are about databases? What's the point of DBA.SE being more visible if it means more of that rubbish? I realise that you seem to think this community is stagnant – I clearly cannot see that. I guess it's a matter of, sorry, perspective. I'm not entirely sure about (c) but if it boils down to "being less elitist", if a little elitism helps the quality, I don't mind.
@EvanCarroll This site is far from dead, and the community is not unhealthy. As far as SE verticals go, we're 13th traffic-wise. We're also not elitist, we just don't want a million crap questions that have been answered a million times over on SO already. We're more or less at the point where the easy stuff has already been answered on here.
Just out of curiosity both of you guys are playing up this same nonsense, how about you both give me an approximation to the signal-to-noise ratio you see on StackOverflow?
Ah, there we go. It's a "troll" game when you ask to quantify bogus claims about "crap questions" by a team that doesn't like concrete definitions because the community should be defined by perspective. After all "if elitism helps the quality" #TeamStatusQuo doesn't mind, they shouldn't have to even establish that quality is an issue.
Ok, so if we can break that down without name calling -- Gordon clearly has an insane amount of devotion. Are the questions he's answering the problem, or the answers themselves?
And to address some other parts of the previous discussion (not sure if I missed reading something), you seem to argue that there are a lot postgres, sql, etc. questions at SE compared with dba.se I'm not sure if I agree but lets say I do for the moment.
Is refusing all sql,postgresql, etc question from SO a solution? I don't hink many would agree. And your attitude, calling every different opinion nonsense, doesn't help persuading others.
In fairness, I'm only calling one opinion nonsense. It keeps coming in different flavors. And, that is that the perspectives of the people asking and answering matter. As if they weren't expert enough. I am concerned if these are crap questions. I've seen some pretty bad questions asked on both sides. They get answered very quick (often by people like Gordon) without getting closed, and then things move on.
@EvanCarroll Yeah, I think we have similar questions/answers here. Do you want me to go and test his answer? because 99% of times I have done it, he had some mistake.
What is the point of adding a foreign key reference when the target table field isn't a primary key? Or does it require that the target table field we are referring to needs a primary key reference?
No, I'm not defending Gordon. But we have to establish whether or not we have solved the Gordon problem, or whether or not we haven't had that problem simply because we're missing all these great questions (like the last one Gordon tried to address) stackoverflow.com/q/40902420/124486
@deostroll Yes, the target column's being the PK is commonly a requirement. In some platforms the target is also allowed to have a unique constraint defined on it, instead of the PK, to allow the FK to be created.
I'm saying I can envision a system where we pick up these questions that Gordon is answering (because I don't think you're right to call them crap, 75-90% of the SO questions are perfectly good, and here it's probably like 90-95% guesstimating). So, SO has more crap, but we're off imho if we pretend like it's most crap, or that we would be better if we picked up their questions that addressed the db subject matter (taking the good with the bad).
Your proposed solution (baning SQL questions from SO) has 2 or 3 problems: First, we have to have dba.se community to agree on that. Second, we have persuade SO to agree on that and stop accepting these questions.
@ypercubeᵀᴹ yes, those are certainly problems. but I think it would be better to have clearer boarders for both and when this convo started we were looking at an mso post where this was evidently a real problem (as others had brought it up) and were trying to address it. I'm just unsatisfied that the defense of the status quo (based on perspective) was right.
@deostroll primary key has nothing to do with foreign key
@EvanCarroll I haven't read back through all the conversation while I was eating, but the two main responses seem to have been well received by both communities.
So in practice, what I would say is that if a question is tagged with postgresql and nothing else (or god forbid, even sql-server) that the question be deemed off limits for Stack Overflow, and suitable for this site.
It's all well and good railing against the "status quo", but the "status quo" has come about by consensus, via a load of professionals that are passionate about databases, that didn't know each other, with no agenda. Don't you think that the way the site has evolved has done so for a reason?
@Philᵀᴹ no, I think it emerged from beta as something that said "database administrators" a bunch of people using Area51 thought it was cool. Jumped on it. And, now it's become confusing to those on SO, and the lack of definition is still a problem (in my eyes and others). You argue that the definition passed consensus, that's not really so in any meaningful fashion. And, even if it, so what? That was years ago, I could still question it. But it didn't. ;)
I mean look at the definition on the proposal: http://area51.stackexchange.com/proposals/4260/database-administrators?phase=definition&tab=active&questions=closed#tab-top
Which one of those questions were closed because they were a typo?
Or because they were too crappy, but would otherwise be welcome on Stack Overflow.
> Very basic questions do still get asked on DBA, and this is perhaps inevitable. These questions are often answered in place rather than being migrated to SO. My feeling is that this is because people want to be helpful. It is easier to answer someone's basic question quickly, rather than waiting for a migration to take effect. This is an ongoing discussion on our site though.
That's my argument in a nut shell. We're missing a lot of good questions, and they wouldn't otherwise be problematic to be asked here. It is however problematic to have good and concrete questions asked on SO because it confuses the users as to what dba.se is serving and doing (if they even know it exists).
@ypercubeᵀᴹ missing questions because people ask them elsewhere could be better defined by helping people understand where to ask them, that's tough when we're still going with the perspective of the questioner. But, if we tell them where to ask them based on subject matter -- problem solved.
Bill will pop in with a conversation-ending work of Photoshop genius any moment no doubt.
2
And to address something from earlier, dba.se continues to grow quite nicely, with one of the better communities around. Most metrics show us in or around the top 10 of se sites.
You know I can see another option for DBA.StackExchange. If we're going to continue to be elitists and ban "Simple SQL" questions, can we also ban simple sql backends like MS SQL sql-server?
@PaulWhite yeah, they are quite useful. Were you referring to this answer? dba.stackexchange.com/questions/152427/… (where we avoid deferrable constraints by inserting in a single statement)
So show your support and take the #MustardChallenge. Drinking mustard is not too much of a sacrifice for those that would sacrifice everything for you.
The idea behind the latest answer seems to be same as mine. The other contender appears to assume that character data will only consist of single letters. Could suit the OP, the question isn't explicit on that point.
I would like know, how can we re-order the columns in ascending or descending order, while retrieving the data.
Suppose the table contains the data as below with no primary key/unique key constraints:
Col1 Col2 Col3 Col4
---- ---- ---- ----
B D C A
C ...
Hi to you all. Nice being here. Question about a question. Currently I have opened up a question over on Serverfault.com because I thought I would get a good response regarding IP configuration and networking. So far, nothing.
Tl;Dr
I have a SQL Server instance (SQLSERVER01-i01) with a dedicated IP address and port (162.xxx.xxx.51:1433) on a multi-instance SQL Server (each SQL Server instance on the Windows Server has its own IP address) which are all hosted on one Windows server (SQLSERVER01 / 162.xxx.xxx.50).
I a...
Bases on your vast knowledge and understanding of everything surrounding SQL Server, would I get a better response from the dba.stackexchange.com community?
@hot2use That's a very well-asked question. I'm not qualified to say if it would be answered here. One of the others should have an opinion on that, perhaps @TomV?
That said, it's only had 12 views on SF so a bounty is something else to consider in general. We don't have a particularly good record with SSRS questions here.
I'd like to submit my application for this job.
Requirements
Fluency in English and Spanish (native-level writing in Spanish)
I'm not quite fluent in Spanish but I'm willing to learn. I think this should only be a minor setback. Rosetta Stone is discounted to $249 now so the company expens...
Looking around the other SE verticals, it must just be our turn to be trolled for a while until he gets bored. Looks like it's the same shyte over and over again
I have two Sql-Server user accounts on a database that behave differently on INSERT/UPDATE/DELETE.
UserA can do these commands (on any table). It is a Sql-Server 'local' account.
DOMAIN\UserB, cannot. It comes from a Windows AD account. It is a member of Administrators group on the database ser...
There are certainly valid uses of [fstab] on AU.SE. However, 95% of them are probably not valid in being Ubuntu specific. Why not migrate those questions to Unix.SE?
Here is an example of a valid question with this tag
CIFS shares do not mount after upgrade to 12.10 from 12.04
Mount network NT...
@PaulWhite Thanks for the feedback. I'll give the bounty a thought or two. But I'd rather post the question on dba.se and offer a bounty there. (after closing on SF)
@Philᵀᴹ but the suggestion was on opposite direction (there: specific, Ubuntu -> generic, Unix) vs (here: generic, programming, SO -> specific, SQL, Dba.se)
@hot2use Yep no worries. Let me know if you decide to delete and re-ask because I could probably add a more attractive bounty. We can talk more about that if and when.