Re: From BAD To WORSE: A Disasterous Delete

From: Kalen Delaney (replies_at_public_newsgroups.com)
Date: 10/29/04 

Date: Fri, 29 Oct 2004 08:39:14 -0700

I see this when people talk about using EM for data manipulation, because
that's what it does to your data.

John, I suggest you start learning basic SQL soon. EM is a good tool for
working with your objects, but NOT for working with the data itself. 

-- 
HTH
----------------
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in 
message news:OJ90CjcvEHA.1452@TK2MSFTNGP11.phx.gbl...
>> Enterprise Mangler
>
> First time I've seen that one. LOL...
>
> -- 
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
>
> "Geoff N. Hiten" <SRDBA@Careerbuilder.com> wrote in message 
> news:uVR4iYcvEHA.536@TK2MSFTNGP11.phx.gbl...
>> Enterprise Mangler often does a table shuffle under the covers when 
>> making
>> changes to tables.  You can see exactly what it intends to do by saving 
>> the
>> change script before saving changes.  As Tibor points out, many of us 
>> prefer
>> to do things via T-SQL because we know exactly what is happening.  EM is 
>> a
>> good tool, but sometimes the way it wants to do something is not the way 
>> I
>> want it done.
>>
>> -- 
>> Geoff N. Hiten
>> Microsoft SQL Server MVP
>> Senior Database Administrator
>> Careerbuilder.com
>>
>> I support the Professional Association for SQL Server
>> www.sqlpass.org
>>
>> "John Bishop" <ugradfrnd@aol.com> wrote in message
>> news:eDbrR9bvEHA.3896@TK2MSFTNGP09.phx.gbl...
>>> Last night, I posted the message "HELP!:  A Disasterous Delete" (Friday,
>>> October 29, 2004 1:20 AM).  This morning, as I pressed ahead with my 
>>> work
>>> with my smaller data extract, I have had a recurrence of the problem of
>> the
>>> mysterious deletion of ALL RECORDS, but now with the smaller data 
>>> extract.
>>>
>>> But I have a better sense now of what may have CAUSED the problem (I
>> think).
>>> I had just used SQL Server Enterprise Manager to Change the Data Type of
>> two
>>> columns from char to nvarchar.  I was then re-running a query.
>> Thereafter,
>>> in noticed that ALL ROWS of the table seemed to be missing.
>>>
>>> Perhaps I am SPOILED by the way MS Access handles changes to a
>> datastructure
>>> with data records in place.
>>>
>>> DOES SQL 2000 DELETE ALL RECORDS WHEN THE DATA TYPE OF A SINGLE COLUMN 
>>> IS
>>> ALTERED???  This seems like a rather radical treatment to the data 
>>> within
>> a
>>> table if this is the case.
>>>
>>> Now I seem to have lost NOT ONLY the original larger 9 million record 
>>> data
>>> table, but also the smaller 350,000 record data extract.
>>>
>>> Maybe I should just throw in the towel!
>>>
>>> Any suggestions are appreciated!!
>>>
>>>
>>
>>
>
>

Relevant Pages