Post by: CigarBanter on August 03, 2021, 12:03:32 AM
Post by: LuvTooGolf on August 03, 2021, 05:30:09 AM
Post by: LuvTooGolf on August 03, 2021, 05:31:35 AM
Rocky Patel Cargo Churchill - 20/34.99; 40/65.00; 60/89.97
Post by: LuvTooGolf on August 03, 2021, 05:32:30 AM
Door #1 - Romeo 505 Nicaragua Toro - 10/49.99
Door #2 - Obsidian White Noise Toro Extra - 10/34.99
Door #3 - Joya de Nicaragua Copper Toro - 5/24.99
Post by: A Friend of Charlie on August 03, 2021, 06:56:50 AM
Post by: A Friend of Charlie on August 03, 2021, 06:57:03 AM
Post by: A Friend of Charlie on August 03, 2021, 07:00:45 AM
I made the most of it by watching Brazil vs. Mexico in the soccer semis. Another game that ended in penalty kicks.
Next up, more soccer but I'm choosing to go back to bed for a bit. I can always watch the highlights of Japan vs. Spain later.
Post by: LuvTooGolf on August 03, 2021, 07:08:20 AM
The whole family woke up early to see Simone Biles and then it didn't seem to air on any of the channels we have.Sounds like a good morning. Except for your family. Lol
I made the most of it by watching Brazil vs. Mexico in the soccer semis. Another game that ended in penalty kicks.
Next up, more soccer but I'm choosing to go back to bed for a bit. I can always watch the highlights of Japan vs. Spain later.
Post by: LuvTooGolf on August 03, 2021, 08:02:33 AM
Post by: LuvTooGolf on August 03, 2021, 08:03:03 AM
Another chilly morning here. 59 right now, nice crisp breeze coming in the doors and windows.I've actually closed the window down here a couple times, cause it's almost too chilly. Lol
Post by: Travellin Dave on August 03, 2021, 09:37:39 AM
Joe:the epitome of 2sDay deals!
Rocky Patel Cargo Churchill - 20/34.99; 40/65.00; 60/89.97
Post by: Travellin Dave on August 03, 2021, 09:41:05 AM
The whole family woke up early to see Simone Biles and then it didn't seem to air on any of the channels we have.Bet that bronze medal means more to her than all the others.
I made the most of it by watching Brazil vs. Mexico in the soccer semis. Another game that ended in penalty kicks.
Next up, more soccer but I'm choosing to go back to bed for a bit. I can always watch the highlights of Japan vs. Spain later.
Best to watch soccer highlights. Cut out the incessant midfield dribbling and back-passing and the match is only about 10 minutes long.
Post by: Travellin Dave on August 03, 2021, 09:42:57 AM
Sis:Was disappointed with the JdN Copper. Probably my least favorite of the "color" series.
Door #1 - Romeo 505 Nicaragua Toro - 10/49.99
Door #2 - Obsidian White Noise Toro Extra - 10/34.99
Door #3 - Joya de Nicaragua Copper Toro - 5/24.99
Post by: Travellin Dave on August 03, 2021, 09:47:31 AM
Post by: Travellin Dave on August 03, 2021, 09:50:01 AM
There are 150 days left in the year.
Today’s Highlight in History:
On August 3, 1936, Jesse Owens of the United States won the first of his four gold medals at the Berlin Olympics as he took the 100-meter sprint.
On this date:
In 1914, Germany declared war on France at the onset of World War I.
In 1949, the National Basketball Association was formed as a merger of the Basketball Association of America and the National Basketball League.
In 1966, comedian Lenny Bruce, whose raunchy brand of satire and dark humor landed him in trouble with the law, was found dead in his Los Angeles home; he was 40.
In 1972, the U.S. Senate ratified the Anti-Ballistic Missile Treaty between the United States and the Soviet Union. (The U.S. unilaterally withdrew from the treaty in 2002.)
In 1981, U.S. air traffic controllers went on strike, despite a warning from President Ronald Reagan they would be fired, which they were.
In 1993, the Senate voted 96-to-three to confirm Supreme Court nominee Ruth Bader Ginsburg.
In 1994, Arkansas carried out the nation’s first triple execution in 32 years. Stephen G. Breyer was sworn in as the Supreme Court’s newest justice in a private ceremony at Chief Justice William H. Rehnquist’s Vermont summer home.
In 2004, the Statue of Liberty pedestal in New York City reopened to the public for the first time since the 9/11 attacks.
In 2005, fourteen Marines from a Reserve unit in Ohio were killed in a roadside bombing in Iraq.
In 2014, Israel withdrew most of its ground troops from the Gaza Strip in an apparent winding down of a nearly monthlong operation against Hamas that had left more than 1,800 Palestinians and more than 60 Israelis dead.
In 2018, Las Vegas police said they were closing their investigation into the Oct. 1 shooting that left 58 people dead at a country music festival without a definitive answer for why Stephen Paddock unleashed gunfire from a hotel suite onto the concert crowd.
In 2019, a gunman opened fire at a Walmart store in El Paso, Texas, leaving 22 people dead; prosecutors said Patrick Crusius targeted Mexicans in hopes of scaring Latinos into leaving the U.S., and that he had outlined the plot in a screed published online shortly before the attack. (A man who was wounded in the shooting died in April 2020 after months in the hospital, raising the death toll to 23. Crusius has pleaded not guilty to state murder charges; he also faces federal hate crime and gun charges.)
Post by: Travellin Dave on August 03, 2021, 09:50:42 AM
Five years ago: President Barack Obama cut short the sentences of 214 federal inmates, including 67 life sentences, in what the White House called the largest batch of commutations on a single day in more than a century. An Emirates Boeing 777 crash-landed in Dubai and caught fire; all 300 people on board survived, but one firefighter was killed.
One year ago: The St. Louis Cardinals became the second team sidelined by the coronavirus since the shortened baseball season began July 23; seven Cardinals players and six staff members tested positive, causing the team’s four-game series at Detroit to be postponed. (The Miami Marlins would resume play the following day after missing a week of games.) A Norwegian cruise ship line halted all trips after a coronavirus outbreak on one ship infected more than 40 people on board, most of them crew members; the cruise line had been one of the first companies to resume sailing during the pandemic.
Post by: Travellin Dave on August 03, 2021, 09:55:17 AM
Football Hall of Fame coach Marv Levy is 96.
Singer Tony Bennett is 95.
Actor Martin Sheen is 81.
College and Pro Football Hall of Famer Lance Alworth is 81.
Lifestyle guru Martha Stewart is 80.
Singer Beverly Lee (The Shirelles) is 80.
Movie director John Landis is 71.
Actor JoMarie Payton is 71.
Actor Jay North (TV: “Dennis the Menace”) is 70.
Hockey Hall-of-Famer Marcel Dionne is 70.
Actor Philip Casnoff is 67.
Actor John C. McGinley is 62.
Rock singer-musician Lee Rocker (The Stray Cats) is 60.
Actor Lisa Ann Walter is 60.
Rock singer James Hetfield (Metallica) is 58.
Rock singer-musician Ed Roland (Collective Soul) is 58.
Actor Isaiah Washington is 58.
Country musician Dean Sams (Lonestar) is 55.
Rock musician Stephen Carpenter (Deftones) is 51.
Hip-hop artist Spinderella (Salt-N-Pepa) is 50.
Actor Brigid Brannagh is 49.
Actor Michael Ealy is 48.
Country musician Jimmy De Martini (Zac Brown Band) is 45.
NFL quarterback Tom Brady is 44.
Actor Evangeline (ee-VAN’-gel-een) Lilly is 42.
Actor Mamie Gummer is 38.
Olympic gold medal swimmer Ryan Lochte is 37.
Country singer Whitney Duncan is 37.
Actor Jon Foster is 37.
Actor Georgina Haig is 36.
Actor Tanya Fischer is 36.
Pop-rock musician Brent Kutzle (OneRepublic) is 36.
Rapper Shelley FKA DRAM is 33.
Post by: Travellin Dave on August 03, 2021, 09:55:46 AM
Post by: Travellin Dave on August 03, 2021, 10:09:01 AM
https://www.espn.com/olympics/trackandfield/story/_/id/31948796/athing-mu-19-wins-gold-us-women-800-meters
Post by: A Friend of Charlie on August 03, 2021, 10:20:21 AM
Quite true.The whole family woke up early to see Simone Biles and then it didn't seem to air on any of the channels we have.Bet that bronze medal means more to her than all the others.
I made the most of it by watching Brazil vs. Mexico in the soccer semis. Another game that ended in penalty kicks.
Next up, more soccer but I'm choosing to go back to bed for a bit. I can always watch the highlights of Japan vs. Spain later.
Best to watch soccer highlights. Cut out the incessant midfield dribbling and back-passing and the match is only about 10 minutes long.
Post by: A Friend of Charlie on August 03, 2021, 10:24:10 AM
The Tony Over/Under for today is 10.I knew 12.
Post by: LuvTooGolf on August 03, 2021, 10:40:25 AM
I was gonna say, that was a pretty stacked list today.The Tony Over/Under for today is 10.I knew 12.
Post by: LuvTooGolf on August 03, 2021, 10:41:36 AM
Post by: A Friend of Charlie on August 03, 2021, 10:50:43 AM
Currently stuck in IT hell. Having trouble with one of my systems, and so far 2 hours in, no idea what's wrong. At least the work load is easy. LolIs it raining?
Post by: LuvTooGolf on August 03, 2021, 11:10:13 AM
Lol, they ARE trying, but this person can't seem to figure out the issue. Nearly 2.5 hours at this point.Currently stuck in IT hell. Having trouble with one of my systems, and so far 2 hours in, no idea what's wrong. At least the work load is easy. LolIs it raining?
Post by: A Friend of Charlie on August 03, 2021, 11:12:22 AM
Did you try rebooting?Lol, they ARE trying, but this person can't seem to figure out the issue. Nearly 2.5 hours at this point.Currently stuck in IT hell. Having trouble with one of my systems, and so far 2 hours in, no idea what's wrong. At least the work load is easy. LolIs it raining?
Post by: bluecollar on August 03, 2021, 11:15:56 AM
Agree, only one good in the color series is redSis:Was disappointed with the JdN Copper. Probably my least favorite of the "color" series.
Door #1 - Romeo 505 Nicaragua Toro - 10/49.99
Door #2 - Obsidian White Noise Toro Extra - 10/34.99
Door #3 - Joya de Nicaragua Copper Toro - 5/24.99
Post by: bluecollar on August 03, 2021, 11:20:13 AM
Post by: bluecollar on August 03, 2021, 11:20:53 AM
Is Dean having some type of procedure this week? Maybe someone can PM me???I don't know how that emoji got in there.
Post by: LuvTooGolf on August 03, 2021, 11:21:24 AM
And deleting my cookies, too!Did you try rebooting?Lol, they ARE trying, but this person can't seem to figure out the issue. Nearly 2.5 hours at this point.Currently stuck in IT hell. Having trouble with one of my systems, and so far 2 hours in, no idea what's wrong. At least the work load is easy. LolIs it raining?
Post by: Travellin Dave on August 03, 2021, 11:23:42 AM
Well look at you!The Tony Over/Under for today is 10.I knew 12.
Post by: LuvTooGolf on August 03, 2021, 11:24:13 AM
Is Dean having some type of procedure this week? Maybe someone can PM me???His procedure is on the 11th.
Post by: Travellin Dave on August 03, 2021, 11:25:30 AM
Is Dean having some type of procedure this week? Maybe someone can PM me???Morning Rick.
I believe it's next week.....12th if I recall.
Tendon repair.
Post by: Travellin Dave on August 03, 2021, 11:26:05 AM
Well....12th was close....Is Dean having some type of procedure this week? Maybe someone can PM me???Morning Rick.
I believe it's next week.....12th if I recall.
Tendon repair.
Post by: Travellin Dave on August 03, 2021, 11:28:18 AM
Young woman from Trenton, NJ won the 800M in 1 minute 56.21 seconds.First woman from NJ to win Olympic gold in track. That may be short lived however as Sydney Mclaughlin runs the 400M hurdles later.
https://www.espn.com/olympics/trackandfield/story/_/id/31948796/athing-mu-19-wins-gold-us-women-800-meters
Post by: bluecollar on August 03, 2021, 11:35:27 AM
Good morning and thank you guys.Is Dean having some type of procedure this week? Maybe someone can PM me???Morning Rick.
I believe it's next week.....12th if I recall.
Tendon repair.
Post by: LuvTooGolf on August 03, 2021, 11:36:16 AM
Young woman from Trenton, NJ won the 800M in 1 minute 56.21 seconds.Perhaps she was envisioning some pork roll at the finish line? It would work for me.
https://www.espn.com/olympics/trackandfield/story/_/id/31948796/athing-mu-19-wins-gold-us-women-800-meters
Post by: A Friend of Charlie on August 03, 2021, 11:40:03 AM
Is Dean having some type of procedure this week? Maybe someone can PM me???I don't know the details but I recall he said there was a surgery on the 11th.
Post by: A Friend of Charlie on August 03, 2021, 11:43:21 AM
I was a little late to reply, once again.Good morning and thank you guys.Is Dean having some type of procedure this week? Maybe someone can PM me???Morning Rick.
I believe it's next week.....12th if I recall.
Tendon repair.
Post by: Travellin Dave on August 03, 2021, 12:24:33 PM
What more motivation does ANYONE need???Young woman from Trenton, NJ won the 800M in 1 minute 56.21 seconds.Perhaps she was envisioning some pork roll at the finish line? It would work for me.
https://www.espn.com/olympics/trackandfield/story/_/id/31948796/athing-mu-19-wins-gold-us-women-800-meters
Post by: A Friend of Charlie on August 03, 2021, 12:26:01 PM
You're motivating me now.What more motivation does ANYONE need???Young woman from Trenton, NJ won the 800M in 1 minute 56.21 seconds.Perhaps she was envisioning some pork roll at the finish line? It would work for me.
https://www.espn.com/olympics/trackandfield/story/_/id/31948796/athing-mu-19-wins-gold-us-women-800-meters
Post by: razgueado on August 03, 2021, 12:37:11 PM
Post by: razgueado on August 03, 2021, 12:39:40 PM
12 here to, using the criteria I could describe them from memory. I get 13 if you count that I've heard the guy from Collective Soul on the radio.Well look at you!The Tony Over/Under for today is 10.I knew 12.
This is a competition, right?
Post by: razgueado on August 03, 2021, 12:59:10 PM
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
Post by: LuvTooGolf on August 03, 2021, 01:11:12 PM
So here's the story of the last week. Last Tuesday at 9am people at work went apeshit. The Washington Electronic Lab Reporting System suddenly was discovered to be processing data at half speed. Shit. I pull up the server dashboards. Everything looks normal. One of my guys notices that our twice-weekly index rebuild job on that server has been failing for weeks, and before I can stop him he shares that information. Now all the ape-shit is flying and fingers are pointing in my direction. Good times. And my guy is manually rebuilding indexes all over the place.Sounds like whatever rain was holding up the issue finally let up. Sounds like a rough week, though.
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
Post by: razgueado on August 03, 2021, 01:21:43 PM
Boy, howdy. Probably took a year or two off my life. I even smoked most of a pack of cigarettes. By midnight Saturday night I was pretty convinced I was losing my mind.So here's the story of the last week. Last Tuesday at 9am people at work went apeshit. The Washington Electronic Lab Reporting System suddenly was discovered to be processing data at half speed. Shit. I pull up the server dashboards. Everything looks normal. One of my guys notices that our twice-weekly index rebuild job on that server has been failing for weeks, and before I can stop him he shares that information. Now all the ape-shit is flying and fingers are pointing in my direction. Good times. And my guy is manually rebuilding indexes all over the place.Sounds like whatever rain was holding up the issue finally let up. Sounds like a rough week, though.
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
Post by: A Friend of Charlie on August 03, 2021, 01:22:04 PM
I didn't count Collective Soul dude.12 here to, using the criteria I could describe them from memory. I get 13 if you count that I've heard the guy from Collective Soul on the radio.Well look at you!The Tony Over/Under for today is 10.I knew 12.
This is a competition, right?
Post by: razgueado on August 03, 2021, 01:31:35 PM
Well, I didn't either, because I have no clue what the guy looks like. But I've heard him on the radio.I didn't count Collective Soul dude.12 here to, using the criteria I could describe them from memory. I get 13 if you count that I've heard the guy from Collective Soul on the radio.Well look at you!The Tony Over/Under for today is 10.I knew 12.
This is a competition, right?
Post by: bluecollar on August 03, 2021, 01:40:59 PM
I hear ya brother. I'm on a 17 hour shift. There is more work than we can handle. I am down 5 guys from before Covid. Management replaced no one. It's now time to take action against my employer.Boy, howdy. Probably took a year or two off my life. I even smoked most of a pack of cigarettes. By midnight Saturday night I was pretty convinced I was losing my mind.So here's the story of the last week. Last Tuesday at 9am people at work went apeshit. The Washington Electronic Lab Reporting System suddenly was discovered to be processing data at half speed. Shit. I pull up the server dashboards. Everything looks normal. One of my guys notices that our twice-weekly index rebuild job on that server has been failing for weeks, and before I can stop him he shares that information. Now all the ape-shit is flying and fingers are pointing in my direction. Good times. And my guy is manually rebuilding indexes all over the place.Sounds like whatever rain was holding up the issue finally let up. Sounds like a rough week, though.
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
Post by: A Friend of Charlie on August 03, 2021, 01:42:27 PM
So here's the story of the last week. Last Tuesday at 9am people at work went apeshit. The Washington Electronic Lab Reporting System suddenly was discovered to be processing data at half speed. Shit. I pull up the server dashboards. Everything looks normal. One of my guys notices that our twice-weekly index rebuild job on that server has been failing for weeks, and before I can stop him he shares that information. Now all the ape-shit is flying and fingers are pointing in my direction. Good times. And my guy is manually rebuilding indexes all over the place.That sounds like a very familiar story. When in doubt, blame the storage team.
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
Post by: A Friend of Charlie on August 03, 2021, 01:46:32 PM
The more you bend over backwards for them, the more they'll shit on you.I hear ya brother. I'm on a 17 hour shift. There is more work than we can handle. I am down 5 guys from before Covid. Management replaced no one. It's now time to take action against my employer.Boy, howdy. Probably took a year or two off my life. I even smoked most of a pack of cigarettes. By midnight Saturday night I was pretty convinced I was losing my mind.So here's the story of the last week. Last Tuesday at 9am people at work went apeshit. The Washington Electronic Lab Reporting System suddenly was discovered to be processing data at half speed. Shit. I pull up the server dashboards. Everything looks normal. One of my guys notices that our twice-weekly index rebuild job on that server has been failing for weeks, and before I can stop him he shares that information. Now all the ape-shit is flying and fingers are pointing in my direction. Good times. And my guy is manually rebuilding indexes all over the place.Sounds like whatever rain was holding up the issue finally let up. Sounds like a rough week, though.
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
I got a text regarding a work matter yesterday. I told them that I determined it's not worth my vacation time and it could wait until I return. Haven't heard back since.
Edit: I doubt anything will come of it but I'm more than prepared to look for a new job if it comes to that.
Post by: razgueado on August 03, 2021, 01:48:01 PM
On this day in 1977, Radio Shack unveiled the TRS-80 microcomputer. I was living in Irving, Texas at the time, about to start 7th grade.
The TRS-80, and a DECWriter VT-120 in the math lab at Sam Houston Junior High, were the parents of my career in Information Technology. My five-year detour into ministry and social work, in the end, were a minor detour.
The grandparents of my career were Star Trek and the programmable accounting machines my dad sold for Olivetti in San Francisco in the very early 1970's. I was born at the ass end of Silicon Valley. There must have been something in the water.
I still adore electronic things with buttons that manipulate electromagnetic energy.
Post by: A Friend of Charlie on August 03, 2021, 01:49:39 PM
It appears Travellin' Dave's history review omitted a significant anniversary.I was four years behind you with the IBM PCjr.
On this day in 1977, Radio Shack unveiled the TRS-80 microcomputer. I was living in Irving, Texas at the time, about to start 7th grade.
The TRS-80, and a DECWriter VT-120 in the math lab at Sam Houston Junior High, were the parents of my career in Information Technology. My five-year detour into ministry and social work, in the end, were a minor detour.
The grandparents of my career were Star Trek and the programmable accounting machines my dad sold for Olivetti in San Francisco in the very early 1970's. I was born at the ass end of Silicon Valley. There must have been something in the water.
I still adore electronic things with buttons that manipulate electromagnetic energy.
Post by: razgueado on August 03, 2021, 01:50:05 PM
Ouch. You win. I'm not down any members of my team, and it's exceedingly rare for me to work more than 15 hours. Good luck to you, Rick.I hear ya brother. I'm on a 17 hour shift. There is more work than we can handle. I am down 5 guys from before Covid. Management replaced no one. It's now time to take action against my employer.Boy, howdy. Probably took a year or two off my life. I even smoked most of a pack of cigarettes. By midnight Saturday night I was pretty convinced I was losing my mind.So here's the story of the last week. Last Tuesday at 9am people at work went apeshit. The Washington Electronic Lab Reporting System suddenly was discovered to be processing data at half speed. Shit. I pull up the server dashboards. Everything looks normal. One of my guys notices that our twice-weekly index rebuild job on that server has been failing for weeks, and before I can stop him he shares that information. Now all the ape-shit is flying and fingers are pointing in my direction. Good times. And my guy is manually rebuilding indexes all over the place.Sounds like whatever rain was holding up the issue finally let up. Sounds like a rough week, though.
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
Post by: razgueado on August 03, 2021, 01:55:41 PM
Right? And my new boss tells me in our first meeting, "I know that happens, and I've done it, but it won't happen anymore."So here's the story of the last week. Last Tuesday at 9am people at work went apeshit. The Washington Electronic Lab Reporting System suddenly was discovered to be processing data at half speed. Shit. I pull up the server dashboards. Everything looks normal. One of my guys notices that our twice-weekly index rebuild job on that server has been failing for weeks, and before I can stop him he shares that information. Now all the ape-shit is flying and fingers are pointing in my direction. Good times. And my guy is manually rebuilding indexes all over the place.That sounds like a very familiar story. When in doubt, blame the storage team.
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
A week later he's pointing at me.
I called him on it yesterday. He apologized.
Post by: razgueado on August 03, 2021, 01:58:45 PM
The PCjr was the first computer I ever bought. I bought it from a friend in summer of 1988, when he got himself an IBM 50z. That was the beginning of my pivot back to IT.It appears Travellin' Dave's history review omitted a significant anniversary.I was four years behind you with the IBM PCjr.
On this day in 1977, Radio Shack unveiled the TRS-80 microcomputer. I was living in Irving, Texas at the time, about to start 7th grade.
The TRS-80, and a DECWriter VT-120 in the math lab at Sam Houston Junior High, were the parents of my career in Information Technology. My five-year detour into ministry and social work, in the end, were a minor detour.
The grandparents of my career were Star Trek and the programmable accounting machines my dad sold for Olivetti in San Francisco in the very early 1970's. I was born at the ass end of Silicon Valley. There must have been something in the water.
I still adore electronic things with buttons that manipulate electromagnetic energy.
That computer is still in a closet at my MIL's house in Tucson. I should retrieve it someday.
Post by: LuvTooGolf on August 03, 2021, 02:23:19 PM
Post by: A Friend of Charlie on August 03, 2021, 02:25:12 PM
I sold mine for $400 bucks almost 10 later.The PCjr was the first computer I ever bought. I bought it from a friend in summer of 1988, when he got himself an IBM 50z. That was the beginning of my pivot back to IT.It appears Travellin' Dave's history review omitted a significant anniversary.I was four years behind you with the IBM PCjr.
On this day in 1977, Radio Shack unveiled the TRS-80 microcomputer. I was living in Irving, Texas at the time, about to start 7th grade.
The TRS-80, and a DECWriter VT-120 in the math lab at Sam Houston Junior High, were the parents of my career in Information Technology. My five-year detour into ministry and social work, in the end, were a minor detour.
The grandparents of my career were Star Trek and the programmable accounting machines my dad sold for Olivetti in San Francisco in the very early 1970's. I was born at the ass end of Silicon Valley. There must have been something in the water.
I still adore electronic things with buttons that manipulate electromagnetic energy.
That computer is still in a closet at my MIL's house in Tucson. I should retrieve it someday.
I still have my Commodore Amiga in a box in the garage. It's probably making a nice home for squirrels.
Post by: A Friend of Charlie on August 03, 2021, 02:25:36 PM
Hazzuh!Later, Dave.
Post by: Travellin Dave on August 03, 2021, 02:39:40 PM
So here's the story of the last week. Last Tuesday at 9am people at work went apeshit. The Washington Electronic Lab Reporting System suddenly was discovered to be processing data at half speed. Shit. I pull up the server dashboards. Everything looks normal. One of my guys notices that our twice-weekly index rebuild job on that server has been failing for weeks, and before I can stop him he shares that information. Now all the ape-shit is flying and fingers are pointing in my direction. Good times. And my guy is manually rebuilding indexes all over the place.So you single handedly improved the whole system. Sounds like a promotion to me. Bonus at least!
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
Post by: Travellin Dave on August 03, 2021, 02:42:07 PM
It appears Travellin' Dave's history review omitted a significant anniversary.History is a fluid commodity, and always open for additions and clarifications.
On this day in 1977, Radio Shack unveiled the TRS-80 microcomputer. I was living in Irving, Texas at the time, about to start 7th grade.
The TRS-80, and a DECWriter VT-120 in the math lab at Sam Houston Junior High, were the parents of my career in Information Technology. My five-year detour into ministry and social work, in the end, were a minor detour.
The grandparents of my career were Star Trek and the programmable accounting machines my dad sold for Olivetti in San Francisco in the very early 1970's. I was born at the ass end of Silicon Valley. There must have been something in the water.
I still adore electronic things with buttons that manipulate electromagnetic energy.
...or as in the case recently, alternative realities....
Post by: razgueado on August 03, 2021, 02:54:51 PM
https://www.tshaonline.org/handbook/entries/loma-vista-tx
It notes that the first settler of the Loma Vista area was A D Everett. That would be Andrew Dariot Everett, born in Limestone County, Alabama in 1818, and scion of the Everetts of Virginia who date back in that state to at least 1650.
A D Everett was my great-great-great-great grandfather, on my mom's side. A D was father to Andrew Jackson Everett, who was father to Raleigh Vester Everett, who was father to Robert Lee Everett, whose eldest child was Cathy Elaine Everett, who was my mother.
Raleigh Vester Everett, A D's grandson and my great grandfather, married Lois Etta Geneva Fifield, the daughter of a New Hampshire-born superintendent of a sanitarium in Albuquerque. Lois either purchased or inherited property around Farmington, NM which later in her life was found to contain significant natural gas deposits. I get a small check every year from her estate based on proceeds of the gas leases.
Post by: Travellin Dave on August 03, 2021, 03:04:56 PM
Post by: A Friend of Charlie on August 03, 2021, 03:36:38 PM
While doing some research on my family tree, I came across this web article about Loma Vista, Texas.That's very interesting. I wish I could trace my roots a bit more than I can. I should have asked grandparents and parents a lot more questions when I had the chance. Only have a handful of relatives in the U.S. since I'm first generation.
https://www.tshaonline.org/handbook/entries/loma-vista-tx
It notes that the first settler of the Loma Vista area was A D Everett. That would be Andrew Dariot Everett, born in Limestone County, Alabama in 1818, and scion of the Everetts of Virginia who date back in that state to at least 1650.
A D Everett was my great-great-great-great grandfather, on my mom's side. A D was father to Andrew Jackson Everett, who was father to Raleigh Vester Everett, who was father to Robert Lee Everett, whose eldest child was Cathy Elaine Everett, who was my mother.
Raleigh Vester Everett, A D's grandson and my great grandfather, married Lois Etta Geneva Fifield, the daughter of a New Hampshire-born superintendent of a sanitarium in Albuquerque. Lois either purchased or inherited property around Farmington, NM which later in her life was found to contain significant natural gas deposits. I get a small check every year from her estate based on proceeds of the gas leases.
Post by: A Friend of Charlie on August 03, 2021, 03:38:28 PM
Only have time for one cigar this afternoon, better make it a good one.Not a bad way to go. I'm about to embark in a walking tour around Salem, MA. Doubt I'll find any cigar shops but I'll keep my eyes peeled.
Post by: bluecollar on August 03, 2021, 03:39:35 PM
Thank you RazOuch. You win. I'm not down any members of my team, and it's exceedingly rare for me to work more than 15 hours. Good luck to you, Rick.I hear ya brother. I'm on a 17 hour shift. There is more work than we can handle. I am down 5 guys from before Covid. Management replaced no one. It's now time to take action against my employer.Boy, howdy. Probably took a year or two off my life. I even smoked most of a pack of cigarettes. By midnight Saturday night I was pretty convinced I was losing my mind.So here's the story of the last week. Last Tuesday at 9am people at work went apeshit. The Washington Electronic Lab Reporting System suddenly was discovered to be processing data at half speed. Shit. I pull up the server dashboards. Everything looks normal. One of my guys notices that our twice-weekly index rebuild job on that server has been failing for weeks, and before I can stop him he shares that information. Now all the ape-shit is flying and fingers are pointing in my direction. Good times. And my guy is manually rebuilding indexes all over the place.Sounds like whatever rain was holding up the issue finally let up. Sounds like a rough week, though.
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
Post by: bluecollar on August 03, 2021, 03:45:45 PM
We have called the office of Fuel devices. They enforce the codes. We've had enough.The more you bend over backwards for them, the more they'll shit on you.I hear ya brother. I'm on a 17 hour shift. There is more work than we can handle. I am down 5 guys from before Covid. Management replaced no one. It's now time to take action against my employer.Boy, howdy. Probably took a year or two off my life. I even smoked most of a pack of cigarettes. By midnight Saturday night I was pretty convinced I was losing my mind.So here's the story of the last week. Last Tuesday at 9am people at work went apeshit. The Washington Electronic Lab Reporting System suddenly was discovered to be processing data at half speed. Shit. I pull up the server dashboards. Everything looks normal. One of my guys notices that our twice-weekly index rebuild job on that server has been failing for weeks, and before I can stop him he shares that information. Now all the ape-shit is flying and fingers are pointing in my direction. Good times. And my guy is manually rebuilding indexes all over the place.Sounds like whatever rain was holding up the issue finally let up. Sounds like a rough week, though.
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
I got a text regarding a work matter yesterday. I told them that I determined it's not worth my vacation time and it could wait until I return. Haven't heard back since.
Edit: I doubt anything will come of it but I'm more than prepared to look for a new job if it comes to that.
Post by: A Friend of Charlie on August 03, 2021, 06:17:42 PM
Good for you, Rick. Enough is enough.We have called the office of Fuel devices. They enforce the codes. We've had enough.The more you bend over backwards for them, the more they'll shit on you.I hear ya brother. I'm on a 17 hour shift. There is more work than we can handle. I am down 5 guys from before Covid. Management replaced no one. It's now time to take action against my employer.Boy, howdy. Probably took a year or two off my life. I even smoked most of a pack of cigarettes. By midnight Saturday night I was pretty convinced I was losing my mind.So here's the story of the last week. Last Tuesday at 9am people at work went apeshit. The Washington Electronic Lab Reporting System suddenly was discovered to be processing data at half speed. Shit. I pull up the server dashboards. Everything looks normal. One of my guys notices that our twice-weekly index rebuild job on that server has been failing for weeks, and before I can stop him he shares that information. Now all the ape-shit is flying and fingers are pointing in my direction. Good times. And my guy is manually rebuilding indexes all over the place.Sounds like whatever rain was holding up the issue finally let up. Sounds like a rough week, though.
"Justin," I tell my guy. "The job didn't really fail. I monitor index fragmentation, and I know that all of the WELRS indexes are under 15% fragmented. The job reports an error, but it's on a test database that is the last thing it rebuilds."
"Shit," says Justin.
So now it's all our fault, and, among all the other tasks we're assigned, Justin and I have to now "fix" this, even though it's not our problem. Except Justin isn't on the IMT, so he logs off on Friday night at 6pm, and he goes on leave. So I fight with this bad boy all weekend, and every metric I dig through in SQL Server says the same thing - the server has been performing at the same level for months. There is no explanation for the slowdown in WELRS processing. The application wasn't changed, the database wasn't changed, the server wasn't changed. There's been significant data growth, but it was designed to handle that. I know because my late friend Scott built it. So, yesterday morning, we scream for - I mean, file a support ticket with - Microsoft. And we're waiting for them to answer when, lo and behold, about noon, one of the application guys for WELRS says, "Uh...I'm not sure what's happening here, but processing has returned to normal. It returned to normal at 9am. Did you guys do something?"
"I didn't do shit, and neither did anyone on my team, I can guarantee it!" says I. "Did YOU do something?"
Nobody did anything. And by end of day, not only had processing returned to "normal," it had returned to the performance level it had when the data was half the size it is now. No explanation. No change in the code. No change in the SQL Server. No change in the database. At 9am last Tuesday the system started processing data at half speed. At 9am yesterday it returned to normal. Better than normal.
And this is what fucked up my weekend and the vacation I'm supposed to be on.
I got a text regarding a work matter yesterday. I told them that I determined it's not worth my vacation time and it could wait until I return. Haven't heard back since.
Edit: I doubt anything will come of it but I'm more than prepared to look for a new job if it comes to that.
Post by: Travellin Dave on August 03, 2021, 09:26:04 PM
While doing some research on my family tree, I came across this web article about Loma Vista, Texas.Fascinating family history to look back on! I can only go back three generations then leap to Welsh coal mines and Eastern Europe black holes.
https://www.tshaonline.org/handbook/entries/loma-vista-tx
It notes that the first settler of the Loma Vista area was A D Everett. That would be Andrew Dariot Everett, born in Limestone County, Alabama in 1818, and scion of the Everetts of Virginia who date back in that state to at least 1650.
A D Everett was my great-great-great-great grandfather, on my mom's side. A D was father to Andrew Jackson Everett, who was father to Raleigh Vester Everett, who was father to Robert Lee Everett, whose eldest child was Cathy Elaine Everett, who was my mother.
Raleigh Vester Everett, A D's grandson and my great grandfather, married Lois Etta Geneva Fifield, the daughter of a New Hampshire-born superintendent of a sanitarium in Albuquerque. Lois either purchased or inherited property around Farmington, NM which later in her life was found to contain significant natural gas deposits. I get a small check every year from her estate based on proceeds of the gas leases.
Post by: Travellin Dave on August 03, 2021, 09:27:21 PM
Don't waste your time in Plymouth. Just a tourist trap.Only have time for one cigar this afternoon, better make it a good one.Not a bad way to go. I'm about to embark in a walking tour around Salem, MA. Doubt I'll find any cigar shops but I'll keep my eyes peeled.
Post by: Travellin Dave on August 03, 2021, 09:31:02 PM
Post by: A Friend of Charlie on August 03, 2021, 11:37:57 PM
Heading to Newport, RI tomorrow.Don't waste your time in Plymouth. Just a tourist trap.Only have time for one cigar this afternoon, better make it a good one.Not a bad way to go. I'm about to embark in a walking tour around Salem, MA. Doubt I'll find any cigar shops but I'll keep my eyes peeled.