November 24, 2015 at 6:02 am
ThomasRushton (11/24/2015)
Ed Wagner (11/23/2015)
Brandie Tarvin (11/23/2015)
I have the simplest error-handling method in the universe:Is there an error?
DROP DATABASE <problemDB>;
Done.
I like that. Perhaps a more individualized approach would be to drop the login of the troublemaker. They wouldn't complain about the error. By the time they filled out the requisite stack of forms to get permission and approval for what they need, the developer might have the problem fixed for real. 😛
Me, I'm heading down the path of nuking the server completely. But I'm in the wonderful world of being able to rebuild and redeploy a server with just a couple of Powershell scripts. 🙂
I long for the days when I could get a server stood up in less than a couple weeks...
Here, it takes about a week for the request for the server (VMs, mind you, not physicals) approved, at least 2 weeks before the server guys release it (has to be installed, updated, checked, updated again, checked, plus a few other steps,) THEN I can start installing SQL...
November 24, 2015 at 6:18 am
ThomasRushton (11/24/2015)
Ed Wagner (11/23/2015)
Brandie Tarvin (11/23/2015)
I have the simplest error-handling method in the universe:Is there an error?
DROP DATABASE <problemDB>;
Done.
I like that. Perhaps a more individualized approach would be to drop the login of the troublemaker. They wouldn't complain about the error. By the time they filled out the requisite stack of forms to get permission and approval for what they need, the developer might have the problem fixed for real. 😛
Me, I'm heading down the path of nuking the server completely. But I'm in the wonderful world of being able to rebuild and redeploy a server with just a couple of Powershell scripts. 🙂
Don't suppose you'd be willing to share those scripts? @=)
November 24, 2015 at 6:19 am
jasona.work (11/24/2015)
ThomasRushton (11/24/2015)
Me, I'm heading down the path of nuking the server completely. But I'm in the wonderful world of being able to rebuild and redeploy a server with just a couple of Powershell scripts. 🙂I long for the days when I could get a server stood up in less than a couple weeks...
Here, it takes about a week for the request for the server (VMs, mind you, not physicals) approved, at least 2 weeks before the server guys release it (has to be installed, updated, checked, updated again, checked, plus a few other steps,) THEN I can start installing SQL...
Depending on the admin's availability, I can get a VM spun up, ready for SQL in anything between a couple hours and 2 days (and the latter usually with apologies for the delay). That's local on our servers, not Azure. Azure's even faster.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 24, 2015 at 6:39 am
GilaMonster (11/24/2015)
jasona.work (11/24/2015)
ThomasRushton (11/24/2015)
Me, I'm heading down the path of nuking the server completely. But I'm in the wonderful world of being able to rebuild and redeploy a server with just a couple of Powershell scripts. 🙂I long for the days when I could get a server stood up in less than a couple weeks...
Here, it takes about a week for the request for the server (VMs, mind you, not physicals) approved, at least 2 weeks before the server guys release it (has to be installed, updated, checked, updated again, checked, plus a few other steps,) THEN I can start installing SQL...
Depending on the admin's availability, I can get a VM spun up, ready for SQL in anything between a couple hours and 2 days (and the latter usually with apologies for the delay). That's local on our servers, not Azure. Azure's even faster.
At some point, I really need to start mucking about with Azure, just for my own knowledge. I *know* we're never going to move to any commercial cloud / hosting provider, so I won't get a chance to "play" with it through work...
Up next on my holiday spending spree, an MSDN subscription of my very own!
😀
November 24, 2015 at 8:06 am
Steve Jones - SSC Editor (11/20/2015)
Brandie Tarvin (11/20/2015)
Nothing like staying up late two nights in a row to do releases, get called back ten minutes after the second release to be told I forgot to move scripts, and then have a brisk discussion with everyone involved to explain why those scripts didn't get moved.ME: "Those scripts weren't on the move sheet and I don't move anything that I wasn't told to move."
Others: "But the scripts are in X folder."
ME: "Lots of scripts are in that folder. I am not going to run every script in that folder because some of them aren't ready to be moved yet. And you haven't given me a list of scripts to run, and there is nothing from the Y team indicating that there are additional scripts to run. Sorry. Not breaking production on your say so."
It wasn't quite that bad, but I'm exhausted this morning and everyone's running around here in semi-panic mode. "Where are the scripts?"
This is why we preach the pipeline and automation at Redgate (and I've done at other jobs). This is the type of stuff that should be caught in QA or a staging/pre-prod environment. Then whatever is run there is run in prod.
I'll vote with Steve on this one. My company just started leveraging Red Gate SQL Source Control and DLM for CI and, while some teams are experiencing bumps (mainly due to the original repo having deprecated objects), I've had great success using it in a green field project. Being able to check out a Git branch and just deploy the changes in that script folder to the appropriate environment makes for some smooth deploys.
November 24, 2015 at 8:16 am
ThomasRushton (11/24/2015)
Ed Wagner (11/23/2015)
Brandie Tarvin (11/23/2015)
I have the simplest error-handling method in the universe:Is there an error?
DROP DATABASE <problemDB>;
Done.
I like that. Perhaps a more individualized approach would be to drop the login of the troublemaker. They wouldn't complain about the error. By the time they filled out the requisite stack of forms to get permission and approval for what they need, the developer might have the problem fixed for real. 😛
Me, I'm heading down the path of nuking the server completely. But I'm in the wonderful world of being able to rebuild and redeploy a server with just a couple of Powershell scripts. 🙂
Sounds like someone needs to be writing an article about this.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
November 24, 2015 at 8:19 am
jasona.work (11/24/2015)
GilaMonster (11/24/2015)
jasona.work (11/24/2015)
ThomasRushton (11/24/2015)
Me, I'm heading down the path of nuking the server completely. But I'm in the wonderful world of being able to rebuild and redeploy a server with just a couple of Powershell scripts. 🙂I long for the days when I could get a server stood up in less than a couple weeks...
Here, it takes about a week for the request for the server (VMs, mind you, not physicals) approved, at least 2 weeks before the server guys release it (has to be installed, updated, checked, updated again, checked, plus a few other steps,) THEN I can start installing SQL...
Depending on the admin's availability, I can get a VM spun up, ready for SQL in anything between a couple hours and 2 days (and the latter usually with apologies for the delay). That's local on our servers, not Azure. Azure's even faster.
At some point, I really need to start mucking about with Azure, just for my own knowledge. I *know* we're never going to move to any commercial cloud / hosting provider, so I won't get a chance to "play" with it through work...
Up next on my holiday spending spree, an MSDN subscription of my very own!
😀
Congratulations on the new member of the family.
November 24, 2015 at 8:35 am
I just installed Virtual Box, and DevOps gave me a virtual machine.
412-977-3526 call/text
November 24, 2015 at 9:09 am
jasona.work (11/24/2015)
GilaMonster (11/24/2015)
jasona.work (11/24/2015)
ThomasRushton (11/24/2015)
Me, I'm heading down the path of nuking the server completely. But I'm in the wonderful world of being able to rebuild and redeploy a server with just a couple of Powershell scripts. 🙂I long for the days when I could get a server stood up in less than a couple weeks...
Here, it takes about a week for the request for the server (VMs, mind you, not physicals) approved, at least 2 weeks before the server guys release it (has to be installed, updated, checked, updated again, checked, plus a few other steps,) THEN I can start installing SQL...
Depending on the admin's availability, I can get a VM spun up, ready for SQL in anything between a couple hours and 2 days (and the latter usually with apologies for the delay). That's local on our servers, not Azure. Azure's even faster.
At some point, I really need to start mucking about with Azure, just for my own knowledge. I *know* we're never going to move to any commercial cloud / hosting provider, so I won't get a chance to "play" with it through work...
Up next on my holiday spending spree, an MSDN subscription of my very own!
😀
I'm going to be looking into this as well. The decision now is purchase or subscription?
November 24, 2015 at 9:13 am
Brandie Tarvin (11/23/2015)
Luis Cazares (11/23/2015)
Is it me or many people don't really understand error handling or why and how to use try...catch...?It's not just you. Though, to be fair, Try...Catch probably caught a lot of people off guard because they don't use other programming languages and only know as much T-SQL as they can get away with knowing to do their job.
People who use other programming languages generally aren't a lot better. Error management, containment, logging, reporting, diagnosis and recovery are black arts to the typical developer. Even so-called experts (ranging from "SQL experts" to "Extreme Programming in C++ experts") preach nonsense like "attempt no containment, just let it fail because that makes finding and fixing the fault easier". Of course real experts preach a slightly different story: "if you don't know what to do in a catch block, don't claim competence to write any code that needs to detect and manage errors (or indeed attempt to do any sort of error management at all)"
Tom
November 24, 2015 at 9:22 am
Lynn Pettis (11/24/2015)
jasona.work (11/24/2015)
GilaMonster (11/24/2015)
jasona.work (11/24/2015)
ThomasRushton (11/24/2015)
Me, I'm heading down the path of nuking the server completely. But I'm in the wonderful world of being able to rebuild and redeploy a server with just a couple of Powershell scripts. 🙂I long for the days when I could get a server stood up in less than a couple weeks...
Here, it takes about a week for the request for the server (VMs, mind you, not physicals) approved, at least 2 weeks before the server guys release it (has to be installed, updated, checked, updated again, checked, plus a few other steps,) THEN I can start installing SQL...
Depending on the admin's availability, I can get a VM spun up, ready for SQL in anything between a couple hours and 2 days (and the latter usually with apologies for the delay). That's local on our servers, not Azure. Azure's even faster.
At some point, I really need to start mucking about with Azure, just for my own knowledge. I *know* we're never going to move to any commercial cloud / hosting provider, so I won't get a chance to "play" with it through work...
Up next on my holiday spending spree, an MSDN subscription of my very own!
😀
I'm going to be looking into this as well. The decision now is purchase or subscription?
I believe, even the "purchase" is a "subscription" in that you need to renew it every year to continue getting the software and benefits. The new "subscription" version is a month-to-month plan...
Sort of like the difference between a cell phone contract and a month-to-month pay-as-you-go cell phone...
November 24, 2015 at 3:23 pm
Can anyone tell me why spammer, oops, I meant user, live068 has not been killed yet?
Looks like it's spam ll you want day today.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
November 24, 2015 at 3:25 pm
Alvin Ramard (11/24/2015)
Can anyone tell me why spammer, oops, I meant user, live068 has not been killed yet?Looks like it's spam ll you want day today.
Oops, looks like he might have been killed as I was posting my comment.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
November 24, 2015 at 6:22 pm
Alvin Ramard (11/24/2015)
Alvin Ramard (11/24/2015)
Can anyone tell me why spammer, oops, I meant user, live068 has not been killed yet?Looks like it's spam ll you want day today.
Oops, looks like he might have been killed as I was posting my comment.
That's always a good thing to hear. There's always more than enough to go around, but it sure is nice when it gets whacked.
November 25, 2015 at 5:24 am
So on my way in to work this morning, the news station I listen to has a brief story about a local Toyota dealer running a "promotion." On hearing the deal, I start thinking, maybe it's time to get a Tacoma pickup truck so the wife and I finally can haul something larger than a breadbox.
Then I hear a bit more of the details, namely the "out" for the dealer on the promo...
What's the promo?
Easy. If the U of M Wolverines shutout the Ohio State Buckeyes in the football game on Saturday, the dealer will refund the purchase price of the vehicle.
Of course, reading another story on this, eagle-eyed rules lawyer me noticed some wording:
At Victory Toyota, from now until the end of the month, anyone who buys a vehicle will be paid back the cost of the car or truck, if U of M is able to shut out OSU.
(Emphasis mine)
Maybe after work tonight I'll see if that wording is on the dealers site as well, that way I can wait until *after* the game to decide if it's time to get a pickup truck or not...
:hehe::-D
Viewing 15 posts - 51,586 through 51,600 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply