Help getting rid of sql default tables
-
The thing I find amazing is that someone who claims to be a “senior DBA” would just jump in and do something without having a clue about what they are doing. A DBA should follow the same rule as doctor: Primum non nocere (First, do no harm)
If you really are a “senior DBA” and you tried to do what you claimed, you earned every bit of the abuse that you received.
-
Personally, I think enough has been said. It is obvious that Ryan is new to MS SQL Server, and he made what appeared to be a serious error trying to delete system tables as well as making what to many was an inappropriate comment about a contract worker. Let it go. I pretty sure that after this experience that Ryan will probably exercise due diligence before just running someone elses code before just running it.
How many of us have made what more experienced individuals would consider serious mistakes? We all make mistakes, but that is also how we learn.
-
Ryan,
It appears that your tone has gone down a notch. And I think that we all agree that a couple of comments made by you and others were over the line. I will agree with Lynn here and say let's actually try and help with your issue. I will also try and explain my comment about not knowing what you deleted because I still believe you don't know.
The first question that would be helpful to know would be what is the database name? Is it MASTER?
For the most part, if the table name shows up in a
select * from sys.tables
You can assume that it is not a "System Table" (these aren't secret). You said these were test tables that were prefixed with "sys" If your contractor Truly did this, he deserves worse than we gave you. Unless his initials happen to be "SYS" ... No even then
Do you have any idea why that prefix was chosen? How did you determine that was a prefix to remove tables. I am getting at this because as a developer/dba I can't think of any reason to do that. I would still need to verify that the application doesn't need them. Do you have access to the application code? If someone was foolish enough to prefix a table with "sys" for any reason, how do you know it wasn't used for real?
FYI, 20G is only 10%. And quite honestly I woundn't at all be surprised if you start being nice we might be able to recover even more space.
First thing I would suggest running is "dbcc updateusage('dbname')"
Then try this query.
SELECT
OBJECT_NAME(id),name,dpages,reserved,used FROM sysindexes ORDER BY used desc
-
Hey Bobby,
Case closed on this one. No, it wasn't the Master db, it was our application's db. And yes, the contractor named his test table with a prefix of sys. So I ran a script he had to "select 'drop table ' + object_name(id) from sysobjects where object_name(id) like 'sys%' and type='u'". System tables are, of course, omitted by this statement.
-
You just don't know when to stop. Let me put it this way. If you are under 25, I hope you wise up soon, because this attitude WILL catch up with you. If you are over 50, consider early retirement.
And you dare post this. http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=146&messageid=389856
You really are an AR$E Hope you enjoyed yourself.
-
What are you talking about?
To be honest with you, you're sitting here giving all of this advice, when in turn, you should be following it yourself. Some guy acted like a douche bag and I called him on it. Big deal. Do you let people push you around like that? I sure don't.
-
Ryan, While I seriously diagree with alot of the things said on this thread you have to understand where alot of the confusion came. The title of the thread is "Help getting rid of sql default tables". Not getting rid of user tables named with a sys prefix". That being said can we please stop sniping at each other?
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
-
I have no problem stopping, but I'm the only one being told to do so, and that's where my problem is. No one seems to want to jump and tell anyone else on here to stop, just me. Like I said, I'm not going to sit here and let people talk down to me.
-
Professionalism, sometimes we exhibit it, some times we don't (been there done that; didn't mean much by it but it blew things out of proportion). You can stupe (sp ?) to the level of others or be professional and stand above it. Question for you Ryan, is which are you willing to do? I have been insulted, degraded, etc., and I tried, at least in the public forum, to stay above it.
-
Hi Lynn, you have been very nice and professional throughout this thread, and I appreciate it
I hear what you're saying, but I'm not going to let people talk down to me.
-
Going off-line, check your private messages.
-
My response was based upon what you had written originally. If you were expedient with the necessary detail, that is not our fault. We've simply seen a post where somebody has already nuked some sys tables and is trying to get rid of the rest. We simply called it as we saw it ok (as Lynn, Bob and Steve have pointed out).
What I'm struggling with Ryan, is if you're a Senior DBA, how come this is your first post? Are you new to SQL but come from another RDBMS, like me? I'm Oracle through and through (yes I know boo hiss everyone!) and I only look after MSSS because I have to.
As for the Darwinian theory stuff, sorry but the reality of life is brutal. I've never met a DBA in 15 years of IT, nor have my colleagues with a combined 75 years, who was cavalier or slap dash in their approach. There's a reason for that, and it's Darwinian I'm afraid. If you're a production DBA and you screw up because of poor process, you go out to grass.
But worse than that, and this is why I appealed to the community to close ranks on this, is that a DBA position recently vacated by somebody who shouldn't have been there in the first place, is much more likely to be outsourced. To the Indian sub-continent likely as not. And then some 'little foreign' bloke has now got your job!
-
I'm fine with the "survival of the fittest" mentality. But you went yapping away about how someone who doesn't know what he's talking about shouldn't be "sniffing" around tables prefixed with "sys" because they think they're dev tables. If you would've actually read the thread, then you would have seen that the tables I deleted were in fact dev tables, and not system tables.
And to think a DBA of your ilk jumped to such conclusions.... maybe I'll see you out in the pasture.
-
Ryan - It was NEVER clear to me that in your initial posts you were NOT talking about system tables. By failing to give even one example of the table names you were citing, we had very little to go on. Ambiguous questions get ambiguous answers.
Also, what place does ego have in getting a problem solved? Leave the ego at the door. The people responding (reacting?) to your posts don't know anything about you except what you post here (yes, I checked to see whether you put anything in your profile). Assuming we know more than that leads back to the true spelling of 'ass u me'. It's a two-edged knife (too small to be a sword, and no real blood was spilled).
Thing Dragnet. Just the facts. Leave the emotions out of it, and you will get nonemotional responses. Does your agency offer or require ethnic sensitivity training? I used to work with a gentleman who, in a prior life teamed up with one other person as a 'mutt and jeff' team for the Navy. They had their techniques down so they could get anyone hot under the collar within 30 seconds using ethnic slurs. They then spent the next 3 days explaining why they were slurs, and teaching how to think about language so that unintended slurs could be mostly avoided.
The downside of the existence of such programs is that today ANY slur expressed is presumed to be intentional. We are expected to know better.
And, yes, I know I could have made this shorter, but I'm not going to spend more time on this. Sorry - there are bigger fish to fry.
-
Wow, this has gotten a little crazy, so a few comments and I hope everyone calms down a bit. I wish I had seen this forum a little sooner and stopped some of this.
I have to admit that reading the first few posts I too was skeptical of Ryan being a "Senior DBA" and all the government jokes came to mind. No offense Ryan, but if you read your first post in light of what we've learned, it's obvious why people jumped to that conclusion. Which was wrong and I apologize on behalf of the forum for that.
That being said, there was no reason someone should have picked on your competence as a DBA. You asked a legitimate question and were in fact asking the correct question. It was poor design on your predecessor's part to name tables that way. We've seen similar things in the past with spxxx stored procedures.
However, regardless of your competence or knowledge or position, striking back at someone doesn't speak of professionalism and isn't proving anything. Some jerk calls you names, you haven't defended yourself by calling him names. You're showing you're the same guy.
People generally look to help you out there. Don't let the few jerks out there dictate how you present yourself.
Again, I apologize and no need for a response. Let's move on.
Viewing 15 posts - 46 through 60 (of 61 total)
You must be logged in to reply to this topic. Login to reply