July 3, 2018 at 7:10 am
------------
There is no substitute for hard work - Thomas A. Edison
July 3, 2018 at 7:23 am
Irish88 - Tuesday, July 3, 2018 7:10 AM(new to SQLServerCentral, bear with me)
I have a situation where a SQL Server reboots itself nightly. Looking for answers as to why.
I Googled, "SQL Server restarts, SQL Server Central"First answer listed from SQLServerCentral was a post from "JuanBob" who posted an answer 13 years ago on Monday Nov 28, 2005 at 05:07
(not an indictment; just asking)
How come messages from 13 years pop up when looking for answers when we're using current versions of SQL Server?
I am using SQL Server 2014, (not a version from 2005)When searching for answers on a topic, is there a way in our account configuration settings here in SQLServerCentral.com to display the most recent post related to the topic first as opposed to the oldest post first?Thanks for you assistance.
There is no relationship between SQL Server Central and Google, so whatever order search results are displayed in is down to Google, not SSC.
If you want to search within a specific forum, eg 2017 Administration, navigate to that forum (link) and click on the 'forum search' button.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
July 3, 2018 at 7:39 am
After I was in *SQL Server Central*, JuanBob's answer of 11/28/2005 was listed. I was under the impression that after I was in SSC, it was an SSC issue at that point. (just clarifying)
------------
There is no substitute for hard work - Thomas A. Edison
July 3, 2018 at 7:55 am
Irish88 - Tuesday, July 3, 2018 7:39 AMAfter I was in *SQL Server Central*, JuanBob's answer of 11/28/2005 was listed. I was under the impression that after I was in SSC, it was an SSC issue at that point. (just clarifying)
Exactly how did you perform the search?
In your first post, you mentioned Google. Are you now suggesting that you used some search functionality provided by SSC?
If you really did just Google "SQL Server restarts, SQL Server Central", the search results would be totally under Google's control.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
July 3, 2018 at 8:06 am
Steps taken:
Google Search: "SQL Server restarts, SQL Server Central"
1st result from Google: https://www.sqlservercentral.com/Forums/Topic240072-5-1.aspx
Once I am in SSC, why aren't the most current replies shown first?
------------
There is no substitute for hard work - Thomas A. Edison
July 3, 2018 at 8:38 am
If you do the search in SSC, the results page has a Sort drop down where you can sort by most relevant first or latest first. This means using the search feature in SSC not Google search.
July 3, 2018 at 8:39 am
Irish88 - Tuesday, July 3, 2018 8:06 AMSteps taken:
Google Search: "SQL Server restarts, SQL Server Central"
1st result from Google: https://www.sqlservercentral.com/Forums/Topic240072-5-1.aspx
Once I am in SSC, why aren't the most current replies shown first?
Google doesn't care what page you are viewing when you perform the search, as far as I know. There is no concept of being 'in' anything.
Try doing exactly the same search while you're viewing Twitter, for example, and you should see the same results.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
July 3, 2018 at 8:42 am
Thanks Phil & Lynn. I appreciate your help.
Will come straight to SSC and search internally and that should fix my issue here.
------------
There is no substitute for hard work - Thomas A. Edison
July 3, 2018 at 9:31 am
FWIW, we use Google's API to implement search. The results are default sorted by relevance, but can be changed.
If you search "SQL Server reboot", you'll get things from any version. I'm curious, why would you expect that only recent versions would be shown? There are plenty of people running 2012, 2008, 2005, even 2000 that might still be posting questions and answers?
Not to beat you down, but 2017 is the current version, and MS supports 2016 as the next most recent one. 2014 isn't recent now either.
I agree this can be frustrating and hard, and that's one of the challenges of lots of information and allowing free form posts. Plenty of people don't tag a version in their question (or answer). We break things into forums, but that fails. Forcing people to tag a version would result in most choosing a default of the first one. Relatively few would actually ensure they pick the correct version, but even then, lots of issues/questions/answers apply to multiple versions.
Is there something you'd expect? Think about it and let me know. But consider, if you asked someone here to help you with "sql server restarts", what do you think they'd say?
July 3, 2018 at 10:02 am
------------
There is no substitute for hard work - Thomas A. Edison
July 3, 2018 at 11:11 am
So we do split out by version, but there's no control over posting there. I know if I look for issues with VS2017, I'll sometimes see posts in the same forum that are for VS2015. Humans are slow to adapt, and that's the case here. My question was less in the why of your need, and more in the why because you didn't specify a version in your query.
There's no need for an apology, and I am not complaining or chastising you. I'm trying to understand your point of view and explain mine, which I might not be doing well.
Microsoft has this issue as well, and really, any place that deals with multiple versions of software. How do we easily segment some information for different versions because it's only applicable there while allowing other information to apply to multiple versions?
I'd like to add tagging to these forums, so that people could tag posts as being SQL Server 2014, but also add SQL Server 2016 and SQL Server 2017 if they're applicable. Crowdsourcing can help,but it's always going to lag.
Retiring older information by default is a good idea. As long as everyone knows this is the case. That's hard to socialize among a large group. If my searches never returned pre-2014 (arbitrary, but likely choice) posts, would it be easy to provide a UI that allows you to show older information? Even the basic search UI in Google that hides duplicates or other suspected bad information sometimes gets lots and people don't realize there is more data.
I'm open to listening to thoughts on how to do this better. Just remember this is a hard problem.
July 5, 2018 at 11:29 am
Steve,
Thank you for taking the time to respond. Most certainly, I concur with you that this is indeed a hard problem since so many are working with different versions of SS. Couple that with the different versions of VS and yes indeed, the problem gets complicated rather quickly.
A couple of thoughts came to mind when you mentioned tagging posts by version. While I have never been an admin on a forum, I'm not sure what all sorts of overhead to set up tagging-by-version would entail on the backend. Second, if you retired older information, could that older information be available by version or would it still be by topic?
I'm just tossing ideas/brainstorming to the table here.
------------
There is no substitute for hard work - Thomas A. Edison
July 5, 2018 at 1:54 pm
Tagging is coming (I think) in the upgrade to this forum software. We have that on top of a list, just waiting on a few resources. Tagging for articles is controlled by us (mostly me), but limiting that in search might be hard. We've talked about building some better searching, but that's really a rabbit hole of development. Even Google struggles here.
Hiding older content is something I'd like, but not really sure how to do this. Once tagging comes in, maybe there are some meta search items we can give you a UI for that will pass these to Google and limit searches. If I completely controlled the app and code, maybe we could build something, but I fear it would be a tuning time sync.
If you have ideas, or anyone does, I'm listening.
July 5, 2018 at 2:36 pm
Steve, I'm not sure that I have solutions on the tagging issue since I have not worked with it before, nor have I administered a forum. Like yourself, I would be interested in the thoughts/perspectives of others for their ideas.
If I can turn a corner a bit, I went out to your voiceofthedba blog. On your #SQLCareer post today you mentioned:
>>I think we can help others learn what it’s like to work in our field, either inspiring them to study harder and build more skills, or warn them of the dangers and downsides.<<
This is a very good idea! Studying/Building skills is key. Since I am somewhat new to SQL Server as a DBA, I want to develop good habits of "best practices" since it is always easier to learn good habits early vs. developing bad habits, unlearning them and then correcting them; too much overhead on the latter. I then ventured out to your TSQLTuesday page. More places in which to learn! 🙂 Awesome! I thank you!
------------
There is no substitute for hard work - Thomas A. Edison
July 5, 2018 at 4:37 pm
You are welcome. Hope we see some posts.
For the tagging, I'll think a bit and try to structure the issues as I see them.
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply