Hi Lena,

Thank you for the update and cooperation.

The issue is so strange. Based on my research, when we use GUI to add data
into the table, the SQL Server will also execute insert. and based on your
description, I know that we can use the same SSMS to use the same method to
add data into the same database under another SQL Server instance.

I understand that you have a busy schedule. according to the current
situation, it is OK if it is not convenient to you to involve another
machine to do the test. if it is convenient to you, please send me an email
and the I can create a FTP(workspace) for you to upload the information
requested.

My email address is v-fathan (AT) online (DOT) microsoft.com (remove the onlien)

in order to further diagnose the issue, we need to capture the SQL Server
Profiler Trace. I would like to compare the problematic process(Standard
instance) with the normal process(Express instance). after I receive your
email, I will list the detail steps to captue the profile trace.

I look forward to hearing from you.
Best regards,
Mark Han
Microsoft Online Community Support
Get Secure! - www.microsoft.com/security
================================================== ==
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ==
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ==

Just to add my 2 cents:

I tried this on my SQL Server 2005 Developer (9.0.1399). I used the script
and data given in the original post by Lena.

After creating the table, I did "Open Table" and entered the given data.
After tabbing out of the row, a red exclamation mark was placed in the row
pointer cell. Clicking on it showed the message in the status bar that row
retrieve failed. So I closed the query window, and again opened table. The
inserted data was there.

Then I inserted another row. Same warning. Again closing the window and
reopening showed both the rows. Modified this 2nd row. There was no problem.

However this is the only instance on this m/c.

So I tried this on another m/c, an x64 Vista Premium, which has an instance
of SQL Server 2005 Express installed by the mfgr. Over that I had installed
a SQL Server 2008 Developer Ed (10.0.1600) just to check if the presence of
SQL 2K5 Ex will have any effect. But I got the same warning and behavior.

I don't know if this will be useful.

ThanQ...


"LenaMsdn08" <LenaMsdn08 (AT) newsgroup (DOT) nospam> wrote

Hi ESM,

Thank you for the posting.

According to your description, the issue you meet is different with Lena.

Based on my experience, the issue you meet is by-design and the waring is
just a kind remind, you can savely ingore it. I meet this kind of issue
before.

Thank you again.

Best regards,
Mark Han
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Mark,

A warning is issued, when there is a potential threat / erroneous operation.

Sorry, I am working on SQL server after a gap of 7 years. What are the
issues involved in warning "failed retrieving rows"? Why it is happening
only on insertion and not on editing rows?

ThanQ...


"Mark Han[MSFT]" <v-fathan (AT) online (DOT) microsoft.com> wrote

Hi ESM,

Thank you for the update. sometimes, the warning tis indicate a potential
threat / erroneous operation. however this waring is just a kind remind.

in order to address your concern, I would like to explain my understanding
on this design
To use SSMS to open the table; and enter data into the table, before we
click the next row, these data we enter is not really inserted into the
table. Besdies, sine we are inserting data into the table, there is a lock
trigged on the row. So the SQL Server show a remind with( row retrieve
failed).

Hope the above helpful

Besides, Lena I haven't heard from you for a few days. if it is convenient
to you, could you send me a note to tell me the status of the issue.

I look forward to your update.

Best regards,
Mark Han
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

I just wanted to add to this conversation thread. I have the same
problem and I didn't have it last week.

I have run SSMS on a workstation and on the server itself and have
received the following error when inserting/updating a row:

The updated row has changed or has been deleted since data was last
retrieved.

I was able to modify rows in all of the tables before and now I can't.

After reading through the thread, I have a table with the following
definition:


CREATE TABLE [dbo].[tmpMassEmail](
[id] [int] IDENTITY(1,1) NOT NULL,
[emailto] [varchar](200) NOT NULL,
[emailfrom] [varchar](200) NULL,
[employer_id] [int] NULL,
[email_type] [varchar](50) NULL,
CONSTRAINT [PK_tmpMassEmail] PRIMARY KEY CLUSTERED
(
[id] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY =
OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]


Notice:
1) It has a primary key
2) There are no Text or NText fields

When I capture the info in SQL Profiler, I get the following:

exec sp_executesql N'INSERT INTO tmpMassEmail(emailto) VALUES
(@emailto)',N'@emailto nvarchar(13)',@emailto=N'jack (AT) jack (DOT) com'

When I copy that script into a blank query window, it works.

Add me to the list of people who think that the tool should work as if
it were generating the correct sql behind the scenes like I typed it in.
If I wanted a SQL database that I had to write manual scripts for every
change I made, I would use Oracle.

Let's nail this one down and get it fixed!

Let me know if I can help...

Cheers!

Lonnie

*** Sent via Developersdex http://www.developersdex.com ***

Hi Lonnie

Thank you for the post.

according to your description, yes, you meet the same issue dicussed in the
post and I'm working with Lena by email to further narrow down the issue.

based on my test, in the sql profile trace, I found the same SQL command as
the one you found. So the issue is very strange and hard to re-produce. So
to further narrow down the issue, could you please do the following test.
1 involve a new machine and setup the SQL Server 2005 Client Tool; update
the client tool to SP3 and update the SQL Server to SP3; and then use the
new SSMS installed on the new machine to connect to the SQL Server instance
to see if the issue will heppen.

after the above done, if the issue doesn't happen, the cause of the issue
is that the SSMS doesn't work normally and we might need to re-install the
netframwork.

on the other hand, if the issue still occur, the issue might be related to
the SQL Server instance/database.

2 For the same instance where the issue happens, if you insert into another
database by SSMS, does the issue happen?

I look forward to hearing from you.

Best regards,
Mark Han
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Is there a trigger firing by any chance? Even if it doesn't change any data
in the table, it might still generate the "updated row has changed" error.
If so, adding Set NoCount On at the beginning might help.

"Lonnie Koenig" <lonnie (AT) orlandojobs (DOT) com> wrote

Sorry for the delay... I tried doing some research on this to find a
rhyme or reason and here's what I found...

So, I created a new table:

CREATE TABLE [dbo].[test](
[PK] [int] NOT NULL,
[Test] [varchar](50) NULL,
CONSTRAINT [PK_test] PRIMARY KEY CLUSTERED
(
[PK] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY =
OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]



No defaults or anythings out of the ordinary. This still doesn't work.
There are no triggers, constraints, computed columns or anything...

Still doesn't work...

Cheers!

Lonnie



*** Sent via Developersdex http://www.developersdex.com ***

Sorry for the delay... I have been doing some research on this between
projects... I have a brand new workstation with a unmodified SSMS
client install on it.

Workstation:
Microsoft SQL Server Management Studio 9.00.4035.00
Microsoft Analysis Services Client Tools 2005.090.4035.00
Microsoft Data Access Components (MDAC) 6.1.7600.16385
(win7_rtm.090713-1255)
Microsoft MSXML 3.0 5.0 6.0
Microsoft Internet Explorer 8.0.7600.16385
Microsoft .NET Framework 2.0.50727.4927
Operating System 6.1.7600

Server:
SQL Server Version 9.00.4053.00 SP3 Enterprise Edition

Created a new database (TestDB)

CREATE DATABASE [TestDB] ON PRIMARY
( NAME = N'TestDB', FILENAME = N'D:\{PATH}\TestDB.mdf' , SIZE = 2048KB ,
MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB )
LOG ON
( NAME = N'TestDB_log', FILENAME = N'D:\{PATH}\TestDB_log.ldf' , SIZE =
7168KB , MAXSIZE = 2048GB , FILEGROWTH = 10%)
GO
EXEC dbo.sp_dbcmptlevel @dbname=N'TestDB', @new_cmptlevel=90
GO
IF (1 = FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'))
begin
EXEC [TestDB].[dbo].[sp_fulltext_database] @action = 'disable'
end
GO
ALTER DATABASE [TestDB] SET ANSI_NULL_DEFAULT OFF
GO
ALTER DATABASE [TestDB] SET ANSI_NULLS OFF
GO
ALTER DATABASE [TestDB] SET ANSI_PADDING OFF
GO
ALTER DATABASE [TestDB] SET ANSI_WARNINGS OFF
GO
ALTER DATABASE [TestDB] SET ARITHABORT OFF
GO
ALTER DATABASE [TestDB] SET AUTO_CLOSE OFF
GO
ALTER DATABASE [TestDB] SET AUTO_CREATE_STATISTICS ON
GO
ALTER DATABASE [TestDB] SET AUTO_SHRINK OFF
GO
ALTER DATABASE [TestDB] SET AUTO_UPDATE_STATISTICS ON
GO
ALTER DATABASE [TestDB] SET CURSOR_CLOSE_ON_COMMIT OFF
GO
ALTER DATABASE [TestDB] SET CURSOR_DEFAULT GLOBAL
GO
ALTER DATABASE [TestDB] SET CONCAT_NULL_YIELDS_NULL OFF
GO
ALTER DATABASE [TestDB] SET NUMERIC_ROUNDABORT OFF
GO
ALTER DATABASE [TestDB] SET QUOTED_IDENTIFIER OFF
GO
ALTER DATABASE [TestDB] SET RECURSIVE_TRIGGERS OFF
GO
ALTER DATABASE [TestDB] SET ENABLE_BROKER
GO
ALTER DATABASE [TestDB] SET AUTO_UPDATE_STATISTICS_ASYNC OFF
GO
ALTER DATABASE [TestDB] SET DATE_CORRELATION_OPTIMIZATION OFF
GO
ALTER DATABASE [TestDB] SET TRUSTWORTHY OFF
GO
ALTER DATABASE [TestDB] SET ALLOW_SNAPSHOT_ISOLATION OFF
GO
ALTER DATABASE [TestDB] SET PARAMETERIZATION SIMPLE
GO
ALTER DATABASE [TestDB] SET READ_WRITE
GO
ALTER DATABASE [TestDB] SET RECOVERY FULL
GO
ALTER DATABASE [TestDB] SET MULTI_USER
GO
ALTER DATABASE [TestDB] SET PAGE_VERIFY CHECKSUM
GO
ALTER DATABASE [TestDB] SET DB_CHAINING OFF

Then I created a new table:

CREATE TABLE [dbo].[test](
[PK] [int] NOT NULL,
[Test] [varchar](50) NULL,
CONSTRAINT [PK_test] PRIMARY KEY CLUSTERED
(
[PK] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY =
OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]



Same issue exists. Still cannot edit rows in place.

Thanks!

Lonnie

*** Sent via Developersdex http://www.developersdex.com ***