home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.databases.ms-sqlserver      Notorious Rube Goldberg contraption      19,505 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 18,237 of 19,505   
   Erland Sommarskog to Gene Wirchenko   
   Re: SSMS 2008: Confusing/Incorrect Error   
   13 Apr 11 23:50:35   
   
   XPost: microsoft.public.sqlserver.programming   
   From: esquel@sommarskog.se   
      
   Gene Wirchenko (genew@ocis.net) writes:   
   >   1) I call it up on one table, change one column value (not a key   
   > column) from "Cheque" to "Check".  When I try to exit the row, I get:   
   >   
   > No row was updated.   
   >   
   > The data in row 3 was not committed.   
   > Error Source: Microsoft.SqlServer.Management.DataTools.   
   > Error Message: The row value(s) updated or deleted either do not make   
   > the row unique or they alter multiple rows(2 rows).   
   >   
   > Correct the errors and retry or press ESC to cancel the change(s).   
   > and an OK button.   
      
   I don't that grid, and make all my data modifications with scripts.   
   Scripts can be reusable. And trying to second-guess SSMS which has   
   some funny quirks, is nothing I like.   
      
   Hint: you learn more SQL, if you use scripts.   
      
   I can say whether the error message you got makes sense or not, since   
   I don't know the table or the data.   
      
      
   >   2) After I have run Edit Top 200 Row and have closed it, I can not   
   > rerun my database creation script because the database is supposedly   
   > in use.   
   >   
   >      Have I done something wrong, or is this a bug?   
      
   I would guess this is regular connection pooling. That is, the client   
   API holds the connection for 60 seconds after disconnection so it   
   can be resued. This is nothing specific to SSMS.   
      
   The way out is   
      
   ALTER DATBASE db SET SINGLE_USER WITH ROLLBACK IMMEDIATE   
      
   That kills all connections against the database.   
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca