February 11, 2011 at 7:19 am
Grant Fritchey (2/11/2011)
I don't mind pointing out that Red Gate has a tool that can help with this. It's called SQL Storage Compress.And before you guys start throwing heavy blunt objects at me, notice, no link. I'm just saying is all.
By the way, internally they refer to that software as SSC. It confuses the heck out of me, "Why does SSC need compression? Have we been bad?"
The irony of mentioning compression on this thread. 😀
February 11, 2011 at 7:22 am
GilaMonster (2/11/2011)
Craig Farrell (2/11/2011)
On another note, it's 2 in the morning and I'm still watching this job go so that I can get a project up to QA in the morning. These are the times I hate dev systems being weak in equipment. Takes for frickin' ever for large scale data movement.I'm going to be spending part of the weekend cutting down a prod database for restore in dev, on my laptop. There's not enough space in dev to restore the full prod database (300 GB), no space on any other server I can use, and quite honestly no support from management for doing this. The dev environment is easily 6 months out of date and management's response to that is 'Yes? So?'
No prizes for guessing who this is for...
On the plus side, had a very promising meeting this morning,....
Just suggest getting rid of the dev database entirely and developing in production. Think of the time it will save and the efficiency it will create by not having to move code from dev to QA to testing to production!
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
February 11, 2011 at 7:27 am
GSquared (2/11/2011)
Just suggest getting rid of the dev database entirely and developing in production. Think of the time it will save and the efficiency it will create by not having to move code from dev to QA to testing to production!
QA? What's QA? And a separate testing environment? There's a dev box which is just about a joke and production. There's no QA or test environment, don't be stupid, that costs money.
Most of the developers are working locally on their laptops and just coping whatever they need down from production, and the one BA (who developed the 'I know everything' attitude after a promotion from App Support to Business Analyst) thinks that's the perfect way to go and doesn't see why I'm spending any time doing this.
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
February 11, 2011 at 7:29 am
Greg Edwards-268690 (2/11/2011)
Grant Fritchey (2/11/2011)
I don't mind pointing out that Red Gate has a tool that can help with this. It's called SQL Storage Compress.And before you guys start throwing heavy blunt objects at me, notice, no link. I'm just saying is all.
By the way, internally they refer to that software as SSC. It confuses the heck out of me, "Why does SSC need compression? Have we been bad?"
The irony of mentioning compression on this thread. 😀
HA! I didn't even think about that. Heehee.
February 11, 2011 at 7:30 am
QA is where some developers send their code to see if it works correctly or not. Often they do this without verifying that it works in their development environment. After all, they are developers, not testers.... right?
__________________________________________________
Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills
February 11, 2011 at 7:33 am
What might be called (since he hijacked it) the "nabadan" thread is continuing to be a source of amusement. Brandie's latest attempt (http://www.sqlservercentral.com/Forums/FindPost1062466.aspx)to talk sense to a total lunatic may have some effect on him (more likely he'll just add Brandie's post to the list of posts to which he has posted arrogant, ignorant, inane and insulting replies). Apart from not feeding the troll (naughty girl, Brandie) what else do we do to avoid or discourage such behaviour?
Tom
February 11, 2011 at 7:38 am
The Dixie Flatline (2/11/2011)
QA is where some developers send their code to see if it works correctly or not.
Oh, you mean production. Cool, now I'm clear... :sick:
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
February 11, 2011 at 7:41 am
Tom.Thomson (2/11/2011)
What might be called (since he hijacked it) the "nabadan" thread is continuing to be a source of amusement. Brandie's latest attempt (http://www.sqlservercentral.com/Forums/FindPost1062466.aspx)to talk sense to a total lunatic may have some effect on him (more likely he'll just add Brandie's post to the list of posts to which he has posted arrogant, ignorant, inane and insulting replies). Apart from not feeding the troll (naughty girl, Brandie) what else do we do to avoid or discourage such behaviour?
Lordy, that's still going on?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 11, 2011 at 7:42 am
GilaMonster (2/11/2011)
The Dixie Flatline (2/11/2011)
QA is where some developers send their code to see if it works correctly or not.Oh, you mean production. Cool, now I'm clear... :sick:
ROTFLOL
February 11, 2011 at 9:13 am
Dave Ballantyne (2/10/2011)
Steve ,maybe have a word with a few of the UK MVP's at the summit, see if a London user group could be arranged for when you are around. Just a suggestion, if youve got the time would be great.
If I get there, it will be for an event we'll put on, so hopefully meet some people.
Or just arrange for a happy hour (or happy day?) in London somewhere.
February 11, 2011 at 11:19 am
GilaMonster (2/11/2011)
GSquared (2/11/2011)
Just suggest getting rid of the dev database entirely and developing in production. Think of the time it will save and the efficiency it will create by not having to move code from dev to QA to testing to production!QA? What's QA? And a separate testing environment? There's a dev box which is just about a joke and production. There's no QA or test environment, don't be stupid, that costs money.
Most of the developers are working locally on their laptops and just coping whatever they need down from production, and the one BA (who developed the 'I know everything' attitude after a promotion from App Support to Business Analyst) thinks that's the perfect way to go and doesn't see why I'm spending any time doing this.
Fast and Cheap is all that matters.
Until you crash. Then the reality sets in.
February 11, 2011 at 11:42 am
Steve Jones - SSC Editor (2/11/2011)
Or just arrange for a happy hour (or happy day?) in London somewhere.
Now THAT sounds like a plan 🙂
February 11, 2011 at 12:59 pm
GilaMonster (2/11/2011)
The Dixie Flatline (2/11/2011)
QA is where some developers send their code to see if it works correctly or not.Oh, you mean production. Cool, now I'm clear... :sick:
Hm, I don't ever remember working in South Africa but I certainly believe I know which job you inherited from me... you poor, poor thing. I hate nightmare positions like that.
Me: "Best practice is to keep your backups on different drives than your real databases."
Manager: "Who's best practice?"
Me: "Um, everyones?"
Manager: ...everyone jumps off a bridge comment.
Me: "... Here's my two week notice."
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
February 11, 2011 at 2:47 pm
The Dixie Flatline (2/11/2011)
QA is where some developers send their code to see if it works correctly or not. Often they do this without verifying that it works in their development environment. After all, they are developers, not testers.... right?
Bob, you scare me. Seriously. I finally understand some of the goings-on between our project requests and what comes back. Wow. Comprehension dawns on a bleak horizon...
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
February 11, 2011 at 2:50 pm
jcrawf02 (2/11/2011)
The Dixie Flatline (2/11/2011)
QA is where some developers send their code to see if it works correctly or not. Often they do this without verifying that it works in their development environment. After all, they are developers, not testers.... right?Bob, you scare me. Seriously. I finally understand some of the goings-on between our project requests and what comes back. Wow. Comprehension dawns on a bleak horizon...
Heheh, I missed this comment earlier. What, you mean the regression smoke testing in QA isn't how we make sure our proc doesn't have typos?!
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
Viewing 15 posts - 23,911 through 23,925 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply