Just make sure you properly credit the query’s author and link back to the query’s page. When I wanna find real-world queries to show for tuning examples, it’s a great place to start. It’s real data from real humans – just like your day job – and it’s fantastically unreliable and fun.ĭ has lots of useful queries. Again, note the lumpy data distribution – this database is absolutely fantastic for lumpy distribution by date, time, scores, lengths of strings, you name it. Posts are more than just questions and answers, too – the dbo.PostTypes table lists other kinds of posts, like Wiki, TagWiki, TagWikiExcerpt. Note that I’m using a left outer join because not all questions have answers. Most of Stack’s tables are fairly intuitive, but this one is a bit of a gotcha. If you want to do a parameter sniffing demo or show wild swings in data distribution, 22656 is your man.ĭbo.Posts contains both questions and answers. He’s user id #22656, and that’s one number you’ll probably end up memorizing. Jon Skeet is a legendary user at Stack Overflow with over a million reputation points. Speaking of 22656, Jon Skeet’s data is unusual. Simply drop off the strings at the end of the URLs, and these work as well, making it really fun to show the pages of the data you’re looking at: Look at your URL bar in your browser as you’re surfing, and you’ll start to recognize what’s going on: That by itself isn’t a big deal, but here’s where it gets awesome: Stack Overflow’s URLs are all driven by that key. You’re also welcome to distribute that database yourself.Įvery table has Id as a clustering key. Your attendees can download it from /go/querystack as a 1GB zip file with a SQL 2008 database, and then extract it to the full database. It doesn’t change, so you don’t have to worry about updating your screenshots and metrics every time Stack releases a new data dump. This smaller 10GB database has data from the first years of Stack Overflow’s history. Here’s a quick list of things to know.įor stable demos, use StackOverflow2010. Then you have updated your local key for connecting to the remote server for good.You present on SQL Server topics at user groups and conferences, and you’ve been wondering how to get started with the Stack Overflow public database. When prompted with something like are you sure you want to add the host key permanently to this machine? type yes. Now reconnect to your host via ssh, using something like this: ssh -i /Users/ben/document/key.pem /Users/ben/document/key.pem is your server's key pair you had set to use (can't find it anymore? go to the hosting site to regenerate one) and 192.168.0.45 is your remote server IP you are connecting to. Once deletion is done, save it by command Ctrl+ o and quit the file by command Ctrl+ x. No easier way just use your keyboard cursor and backspace or delete keys. You would want to deleted the line mentioned ONLY. The simplest solution would be just deleted the line mentioned (line 74) in your local pc in /var/root/.ssh/known_hosts by sudo nano /var/root/.ssh/known_hosts For security reasons the connection is not established. It says that the remote server host key has changed - therefore your previously stored local record DOES NOT MATCH any more. For instance in the earlier answer: my_mac:~ oivanche$ sudo ssh WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Remove the line from the known_hosts, save changes and reconnect.įor most of the cases, the error msg returned by the Linux would have told you what to do. If you'll read the log more carefully you'll see that the key you've got from a host is conflicting with a key you already have - in this case it's on line 74 of known_hosts file (Offending ECDSA key in /var/root/.ssh/known_hosts:74). Offending ECDSA key in /var/root/.ssh/known_hosts:74ĮCDSA host key for 192.168.0.45 has changed and you have requested strict checking. Please contact your system administrator.Īdd correct host key in /var/root/.ssh/known_hosts to get rid of this message. SHA256:sx1Z4xyGY9venBP6dIHAoBj0VhDOo7TUVCE2xWXpzQk. The fingerprint for the ECDSA key sent by the remote host is It is also possible that a host key has just been changed. Someone could be eavesdropping on you right now (man-in-the-middle attack)! I don't know about your particular situation, but most probably this error came along with a message like this: my_mac:~ oivanche$ sudo ssh WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Just do "sudo vi /var/root/.ssh/known_hosts" and remove the line, that holds a key for a host you're trying to connect to and reconnect again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |