Are the posted questions getting worse?

Question

Are the posted questions getting worse?

Viewing 15 posts - 21,976 through 21,990 (of 66,712 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004363 More actions · Answer 1

CirquedeSQLeil (11/29/2010)
Jeff Moden (11/29/2010)
WayneS (11/29/2010)
CirquedeSQLeil (11/29/2010)
On the flip-side, I see your point and think that weekends are the times for doing deployments. Less impact to the business and make sure we have people to support the deployment.
And compensate those working with equivalent comp time during the week prior/after.
Heh... now THERE's a thought. Just imagine how much better managers would plan if the folks in IT were paid (drum roll, please)... HOURLY!
You have me slobbering over that. Paid hourly would be good for my pocketbook.

Oddly enough, I do get paid by the hour and I still try to not work more than 44 although I'll admit the 71 hours a week ago was pretty sweet. I'd rather have the "down time", though.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

SQLRNNR SSC Guru Points: 281334 More actions · Answer 2

Jeff Moden (11/29/2010)
CirquedeSQLeil (11/29/2010)
Jeff Moden (11/29/2010)
WayneS (11/29/2010)
CirquedeSQLeil (11/29/2010)
On the flip-side, I see your point and think that weekends are the times for doing deployments. Less impact to the business and make sure we have people to support the deployment.
And compensate those working with equivalent comp time during the week prior/after.
Heh... now THERE's a thought. Just imagine how much better managers would plan if the folks in IT were paid (drum roll, please)... HOURLY!
You have me slobbering over that. Paid hourly would be good for my pocketbook.
Oddly enough, I do get paid by the hour and I still try to not work more than 44 although I'll admit the 71 hours a week ago was pretty sweet. I'd rather have the "down time", though.

I could only imagine. I get paid hourly too. My hourly rate is a diminishing rate with the increased hours ;-). The lower my hours, the higher my hourly rate. 😎 Now if I could only figure out how to get that down to <= 40 hrs/wk

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

Jeff Moden (11/29/2010)
Oddly enough, I do get paid by the hour and I still try to not work more than 44 although I'll admit the 71 hours a week ago was pretty sweet. I'd rather have the "down time", though.

Same here. Try being the word in emphasis.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Jeff Moden SSC Guru Points: 1004363 More actions · Answer 4

Changing subjects, have you seen today's featured script? It comes under the category of "Are the featured scripts getting worse"? I try to be tolerant but some of these folks just don't have a clue. I believe I'm going to break out some polite but very high velocity pork chops later on tonight. Here's the link to the script. I find it difficult to believe that anyone gave it a rating of higher than 1.

http://www.sqlservercentral.com/scripts/String+Manipulation/71602/

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Grant Fritchey SSC Guru Points: 398890 More actions · Answer 5

Jeff Moden (11/30/2010)
Changing subjects, have you seen today's featured script? It comes under the category of "Are the featured scripts getting worse"? I try to be tolerant but some of these folks just don't have a clue. I believe I'm going to break out some polite but very high velocity pork chops later on tonight. Here's the link to the script. I find it difficult to believe that anyone gave it a rating of higher than 1.
http://www.sqlservercentral.com/scripts/String+Manipulation/71602/

The scary thing for me is, like some of the more... questionable, articles, these things get high ratings. This one is only at 2.5 stars, but it's at 2.5 stars.

"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

Kit G SSCrazy Points: 2888 More actions · Answer 6

Grant Fritchey (11/30/2010)
Jeff Moden (11/30/2010)
Changing subjects, have you seen today's featured script? It comes under the category of "Are the featured scripts getting worse"? I try to be tolerant but some of these folks just don't have a clue. I believe I'm going to break out some polite but very high velocity pork chops later on tonight. Here's the link to the script. I find it difficult to believe that anyone gave it a rating of higher than 1.
http://www.sqlservercentral.com/scripts/String+Manipulation/71602/
The scary thing for me is, like some of the more... questionable, articles, these things get high ratings. This one is only at 2.5 stars, but it's at 2.5 stars.

And that's one of the reasons why, I always go to the thread for the article/script in question and see what other people say about it, most notably denizens of the Thread.

-- Kit

Grant Fritchey SSC Guru Points: 398890 More actions · Answer 7

Kit G (11/30/2010)
Grant Fritchey (11/30/2010)
Jeff Moden (11/30/2010)
Changing subjects, have you seen today's featured script? It comes under the category of "Are the featured scripts getting worse"? I try to be tolerant but some of these folks just don't have a clue. I believe I'm going to break out some polite but very high velocity pork chops later on tonight. Here's the link to the script. I find it difficult to believe that anyone gave it a rating of higher than 1.
http://www.sqlservercentral.com/scripts/String+Manipulation/71602/
The scary thing for me is, like some of the more... questionable, articles, these things get high ratings. This one is only at 2.5 stars, but it's at 2.5 stars.
And that's one of the reasons why, I always go to the thread for the article/script in question and see what other people say about it, most notably denizens of the Thread.

You do, I do, most of us do, but I don't think everyone else does.

"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

GSquared SSC Guru Points: 260824 More actions · Answer 8

Grant Fritchey (11/30/2010)
Jeff Moden (11/30/2010)
Changing subjects, have you seen today's featured script? It comes under the category of "Are the featured scripts getting worse"? I try to be tolerant but some of these folks just don't have a clue. I believe I'm going to break out some polite but very high velocity pork chops later on tonight. Here's the link to the script. I find it difficult to believe that anyone gave it a rating of higher than 1.
http://www.sqlservercentral.com/scripts/String+Manipulation/71602/
The scary thing for me is, like some of the more... questionable, articles, these things get high ratings. This one is only at 2.5 stars, but it's at 2.5 stars.

It's down to 1.5, and just got another 1 vote.

- 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

Jack Corbett SSC Guru Points: 184394 More actions · Answer 9

Ouch, I hate reading things like this:

http://www.backupexecfaq.com/articles/concepts/backing-up-microsoft-sql-server.html

The last paragraph says:

One unusual element of the Backup Exec SQL Agent is that a full backup does not truncate the log files. If you use SQL's own backup utility, a full backup will backup the database, then truncate the log files. With Backup Exec, you need to run a transaction log backup to truncate the log files. The easiest way to do this is to do a transaction log backup immediately after the full backup.

EDIT: The quoted site is NOT affiliated with Symantec in any way.

I was looking up BackupExec SQLAgent because we are getting some SQL Servers for other centers and I asked about backup plans and they were planning on direct backup to tape using BackupExec, but I don't think that they knew that they needed the SQLAgent to do that. Anyone ever use it? I always recommend against it.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

Chad Crawford SSChampion Points: 11610 More actions · Answer 10

A full backup doesn't truncate the log, and that is a good thing, right? It allows you to take an older full backup, restore all the log files (regardless of whether another full was taken in the middle or not) up to the point in time you are interested in? It's a nice safety feature if something happens to one of the full backup files - just go back one more and start from there. Truncating the log breaks the log chain and leaves a hole (however small it may be) that you can't restore to, right?

Chad

Crud - introduced a technical discussion to the thread, but I'm going to blame it on Jack's quoted reference.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 11

Jack Corbett (11/30/2010)
One unusual element of the Backup Exec SQL Agent is that a full backup does not truncate the log files. If you use SQL's own backup utility, a full backup will backup the database, then truncate the log files. With Backup Exec, you need to run a transaction log backup to truncate the log files. The easiest way to do this is to do a transaction log backup immediately after the full backup.

And we wonder why that myth perpetuates....

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Jack Corbett SSC Guru Points: 184394 More actions · Answer 12

Techinically nothing truncates the log file. In FULL Or Bulk-Logged recovery a log backup frees space in the log file to be re-used and in SIMPLE recovery a checkpoint operation does the same thing.

See Paul Randal's blog for more information. Here's a good starting spot, http://www.sqlskills.com/BLOGS/PAUL/post/A-SQL-Server-DBA-myth-a-day-(3030)-backup-myths.aspx

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

Jack Corbett SSC Guru Points: 184394 More actions · Answer 13

GilaMonster (11/30/2010)
Jack Corbett (11/30/2010)
One unusual element of the Backup Exec SQL Agent is that a full backup does not truncate the log files. If you use SQL's own backup utility, a full backup will backup the database, then truncate the log files. With Backup Exec, you need to run a transaction log backup to truncate the log files. The easiest way to do this is to do a transaction log backup immediately after the full backup.
And we wonder why that myth perpetuates....

Yeah.

I should note that the site that I found that on is NOT affiliated with Symantec in any way. I'll also edit my original post as well.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

Trey Staker SSCarpal Tunnel Points: 4796 More actions · Answer 14

In response to the question about Backup exec:

I used it for a long time. The only issues I had with it were a few versions ago the options for restoring databases were not very intuitive. I used to restore databases to test servers and I was always afraid I'd overwrite the production databases. Never did but every time I had to do it I was scared.

For the past 4 or 5 years I've scripted out my backups in sql agent then let the network guys pick up the files from either the local backup directory of a share on the network. This gives me a lot more control and I don't have to mess with backup exec or pay for the additional be sql agent liscence. I'm not even sure anymore if they still use backup exec or something else.

---------------------------------------------------------------------
Use Full Links:
KB Article from Microsoft on how to ask a question on a Forum

Chad Crawford SSChampion Points: 11610 More actions · Answer 15

Thanks for the clarification - it seemed like such a bold statement of fact, that it made me question for a second. I was thinking maybe there was some change in 2008 that I hadn't heard about (we're still on 2005).

Thanks,

Chad