Help getting rid of sql default tables

  • UPDATE :

    Thanks to the few of you who tried to help. Some of you other guys are just plain nasty to a new poster, so thanks for showing me what this forum is all about.

    Anyways, the tables I deleted apparently weren't sql system tables. The foreign guy who set this db up had a lot of "test" tables that he stupidly prefixed with "sys" (ie:syshistorylogins, sysuserstes). Those are the ones that got deleted, and rightfully so. As some of you pointed out, if you actually try to delete Sql system tables, a critical error is thrown, not allowing you to do so.

    I can understand how some of you feel that "I shouldn't be touching things", etc.... but there are nice ways to say things. Some of you were obviously trying to have fun at my expense, and trying to impress others on the board with your "witty responses". To me, it is you who are the trolls.

  • Ryan - I am SOOOO glad I came in after the shooting was over.

    Just some reminders about how to make this forum more efficient and effective:

    1. Be as specific as possible, without revealing proprietary or private information.

    2. When possible, quote explicit error messages (not applicable to this thread).

    3. When possible, quote SQL code executed or attempted. Examples are like pictures - worth thousands of words in just a few lines of code.

    4. We are struggling in both English and SQL to make ourselves understood to each other. Carry a grain of salt and try to determine what assumptions are not being stated. Sometimes the assumptions matter, sometimes they don't. (e.g., we tend to assume that all questions have a grain of validity in them, no matter how absurd they may seem - you saw evidence of that in this thread)

    Lastly, welcome to the forum, Mr SR DBA! You've been baptized under fire.

    Curiosity question - are you more of an Oracle or Sybase DBA than SQL Server? that detail was glossed over in the volleys flying back and forth.

    Some of the statements you made in your original posting helped to throw folks off track. Those of us who have only worked in private industry have a hard time relating to a government employee's point of view. In my consulting life, I've worked with private, NGO, federal and local government employees and, as a rule, have been pleasantly surprised and impressed with the caliber and dedication of public servants.

    Confession - I suffer racial prejudices. It used to be IBM and COBOL, now it's M$. It's a daily struggle to rise above the prejudice and view the issues before me with an unjaundiced eye, but the occasional rant still slips out.

  • Ryan,

    I must second steve's comments above.  I also think some of the flaming going back and forth could have been avoid had you also taken a few minutes to answer my question at the start.  Also at least 2 or 3 people also asked to see the code you ran.  These two things could have nipped the whole thing in the bud.  I noticed that this thread exploded when it looked like you were attempting to delete system tables.

    What you experienced in this thread is not normal behaviour by the majority of us in this community, as Steve said, think of it as a batizism of fire.  Most of us are here to help in any way we can.

  • I also agree with Steve, but I still don't recall seeing the script   I think it is obvious Ryans experience is not with SQL Server (nor is mine) but an even better comment was the one about "Well stop insulting me an help!!!! It's what you're paid to do!"  Who's getting paid!  If we get paid for this I want a cut.

    Ryan,

    Seriously! You posted getting rid of SQL Default tables.  There are no default tables that take any notable space.  There are a couple of databases installed (couple meg), but that is it.  When you create a new database in SQL Server, it creates a copy of the MODEL database.  If you read the BOL (Books OnLine) that are installed with SQL Server you will find that out.  If you are a newbie, they will be MUCH nicer to you.  However stating that you are a Senior DBA and doing something like this will get you the type of harassment you got.  Even saying I am a Senior DBA (with Oracle) but new to SQL Server, might have helped.  But I don't care what type of DBA you are Senior of however,  everything I have ever worked with has system/metadata tables.  Also, all the tables you had in the origional post are actual system tables.  Again reading the BOL would have explained that.  A senior DBA would know to look that up in the documentation.

    Also, your comments:  "The little foreign guy who was here "helping" last week gave me this script to run. He was deleting all table that had a tbl prefix before them...."

    I am sure that comment inflamed a few people in this forum.  It got me a little hot, and I wouldn't be what I think you would call a little foreign dude.  Stop making Americans look like jerks.  Also, posting the script the individual who was helping you would have helped. 

     

     

  • I'm glad we could help... after all .

    I think this is only fitting, for anyone here, to close this thread .

     

    β€œThe limits of my language are the limits of my world.”

    β€” Ludwig Wittgenstein
  • Hey, sorry if I said "the little foreign guy" but that's what he is!!! He's hard to talk to, and has all these crazy scripts. They say a lot worse things about us, I know because he told me. Sorry I ruffled feathers, but you people said worse things about me!

    I don't want to post any code, but basically it was some crazy stuff that produced a list of sql statements that had "drop table tblName" in it. I just modified it to look for his sys tables, and wondered why there were still some other sys tables sticking around. I now know all about them , and also reduced our overall db size by 21 WHOLE GB'S!!!!!!! Needless to say, my boss was EXTREMELY happy this morning, and even took me out to lunch.

    Thanks for your help dudes, and talk to you later!!!!!

  • So the script was something along the lines of this :

    SELECT 'DROP TABLE [' + USER_NAME(uid) + '].[' + Name + ']' AS DropCMD FROM dbo.SysObjects WHERE XType = 'U' AND Name LIKE sys%' ORDER BY Name

     

    Good thing he didn't wrap it into the exec_resultset system proc .

  • Just remember there, "new poster".... no one called you a "Douche Bag" or "Jive Turkey"... you did.  Suggest you make a little bit of a change, yourself.... even in the face of a little adversity

    --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)

  • Why don't you go back and see who I addressed that too and why. It was much deserving

  • Ryan,

    Apparently you are a little stressed.  Couple things you need to understand. 

    1) This is an INTERNATIONAL Forum.  There are lots of "little Foreign guys (and gals)"  who read this.

    2) This is a USER Exchange (no one get's paid for their advice).

    3) no one deserves being called a names (even you)....

    Now Adam's comments were uncalled for.  However.  I along with him didn't believe you were as advertised, and there was some constructive information there.  Primarily to go look at the manuals because you really are very novice when it comes to SQL Server.  This is coming from a DBA of 10+ years, but I have only worked with SQL Server for about 6 months.

    Hope you enjoyed your lunch.   You may have recovered some space, but you obviously don't have any idea what it was that you deleted.  I really hope you didn't delete anything that WAS really needed. 

    Good luck again.  Based upon your attitude you might want to strongly consider Adams origional suggestion!

     

  • I would not go as far as following Adam's original suggestion, completely.  I would suggest that purchasing some books and some early evening reading would be beneficial.  If your willing, you might also consider purchasing SQL Server 2005 Developers Edition and loading up on a system at home where you can play with it.  It is $50 well spent in my opinion.

  • I know, I know... and even though he was way out of line, you felt you had to follow suit...  and go one better.  Just wanted you to know that the only reason I haven't posted anything to help you is because you really crossed the line with the words you chose to use (and they weren't even directed at me ) .

    --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)

  • Assuming this is a genuine thread (which beggar's belief), then may I suggest that in true Darwinian theory, survival of the fittest should be allowed to take it's course. Yes I know this may seem harsh and not at all altruistic, but by helping this guy you are distorting the DBA gene pool, maybe mankind's!

    I'm all for helping other people, but this guy's beyond help. Think about it, if someone of such below average technical ability, indeed command of the English language (and to think he keeps bagging some foreign bloke - yeah because your grammar is weapons grade mate?!), some how 'works out' that a table prefixed with sys... is really a development or test table not a system one, then he shouldn't be in IT, let alone at it's technical apex.

    Please guys, cast him adrift on the sea of fate and just hope that the guy who was daft enough to hire him, isn't so stupid not to sack him.

    All this guy needs is a can of toughen the heck up and to find his true calling in life. Senior DBA my ar$e!

    Epilogue - In response to a couple of PMs I've received (and no doubt more to follow), yes maybe a bit harsh, so sorry for offending any sensitive types out there. However, if your sensibilities are up to it, have a read of the Selfish Gene by Prof Richard Dawkins and/or the first 10 minutes of a film called Idiocracy, then crystal will become opaque by comparison

  • Ummm, I do know what I deleted. They were tables named by "the contractor" for testing purposes. He prefixed them all with "sys", which in turn is not a good idea, because sql server also prefixes system tables witht his. I admit that I too am new to sql server, and asked about deleting those sys tables. If you actually try to do so, sql throws an error.

    I apologize for the foreign guy comment, although, even you must admit, isn't that harsh. Adam was pretty cruel with his comments, and if you want to side with him, then fine. Just remember that this was my first post on here, EVER, and that's how I was greeted. Also remember that people in this world get called douche bags when they act like one.

  • Well, Mr. "Superior" intelligence, why don't you create a database and see if you can create your own tables prefixed with "sys"? I'll save you the time and tell you that you can. The contractor created a large number of Test tables in our Production database that began with sys. If I'm distorting the DBA gene pool, then it must surely stink to have me correct you.

Viewing 15 posts - 31 through 45 (of 61 total)

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