Error in Identity Column

For some reason my primary key, identity column skipped a couple of numbers. It went from row 734 to 736, 737, 739

Any ideas why this would happen?

thanks

hi

735 & 738 must've been created but deleted somehow.

|||

No, it was not deleted

|||

Rick0194:

No, it was not deleted

Yes they were, that's the only way it could have been skipped. Now, it may be that they get inserted as part of a transaction and something goes wrong and rolls it back -- the identity colum's value will appear to skip the next time a good insert occurs (I just confirmed that on sql 2000)

error in event log

running windows 2003 server, Sql 2000 sp3 and WSS 2.0. I have been getting
the following error. Any ideas on hot to fix it? Also sometimes I cant
connect to the DB using sql mamanger but if I restart the db I can connect.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/9/2004
Time: 3:10:58 PM
User: NA\SqlServerAccount
Computer: CINSQLWSS1
Description:
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 8b 45 00 00 14 00 00 00 ?E.....
0008: 0b 00 00 00 43 00 49 00 ...C.I.
0010: 4e 00 53 00 51 00 4c 00 N.S.Q.L.
0018: 57 00 53 00 53 00 31 00 W.S.S.1.
0020: 00 00 1a 00 00 00 53 00 .....S.
0028: 54 00 53 00 5f 00 63 00 T.S._.c.
0030: 69 00 6e 00 73 00 71 00 i.n.s.q.
0038: 6c 00 77 00 73 00 73 00 l.w.s.s.
0040: 31 00 5f 00 31 00 35 00 1._.1.5.
0048: 30 00 37 00 32 00 35 00 0.7.2.5.
0050: 31 00 38 00 39 00 33 00 1.8.9.3.
0058: 00 00 ..17803 indicates that you are having memory pressure. Depending on what the
SQL error logs say, the pressure could be in the main area (Buffer pool) or
the MemToLeave area.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

error in event log

running windows 2003 server, Sql 2000 sp3 and WSS 2.0. I have been getting
the following error. Any ideas on hot to fix it? Also sometimes I cant
connect to the DB using sql mamanger but if I restart the db I can connect.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/9/2004
Time: 3:10:58 PM
User: NA\SqlServerAccount
Computer: CINSQLWSS1
Description:
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 8b 45 00 00 14 00 00 00 E.....
0008: 0b 00 00 00 43 00 49 00 ...C.I.
0010: 4e 00 53 00 51 00 4c 00 N.S.Q.L.
0018: 57 00 53 00 53 00 31 00 W.S.S.1.
0020: 00 00 1a 00 00 00 53 00 .....S.
0028: 54 00 53 00 5f 00 63 00 T.S._.c.
0030: 69 00 6e 00 73 00 71 00 i.n.s.q.
0038: 6c 00 77 00 73 00 73 00 l.w.s.s.
0040: 31 00 5f 00 31 00 35 00 1._.1.5.
0048: 30 00 37 00 32 00 35 00 0.7.2.5.
0050: 31 00 38 00 39 00 33 00 1.8.9.3.
0058: 00 00 ..
17803 indicates that you are having memory pressure. Depending on what the
SQL error logs say, the pressure could be in the main area (Buffer pool) or
the MemToLeave area.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

error in event log

running windows 2003 server, Sql 2000 sp3 and WSS 2.0. I have been getting
the following error. Any ideas on hot to fix it? Also sometimes I cant
connect to the DB using sql mamanger but if I restart the db I can connect.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/9/2004
Time: 3:10:58 PM
User: NA\SqlServerAccount
Computer: CINSQLWSS1
Description:
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 8b 45 00 00 14 00 00 00 E.....
0008: 0b 00 00 00 43 00 49 00 ...C.I.
0010: 4e 00 53 00 51 00 4c 00 N.S.Q.L.
0018: 57 00 53 00 53 00 31 00 W.S.S.1.
0020: 00 00 1a 00 00 00 53 00 .....S.
0028: 54 00 53 00 5f 00 63 00 T.S._.c.
0030: 69 00 6e 00 73 00 71 00 i.n.s.q.
0038: 6c 00 77 00 73 00 73 00 l.w.s.s.
0040: 31 00 5f 00 31 00 35 00 1._.1.5.
0048: 30 00 37 00 32 00 35 00 0.7.2.5.
0050: 31 00 38 00 39 00 33 00 1.8.9.3.
0058: 00 00 ..17803 indicates that you are having memory pressure. Depending on what the
SQL error logs say, the pressure could be in the main area (Buffer pool) or
the MemToLeave area.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Error Importing Access Report

I am getting a "Reserved Error" message when trying to import a relatively
simple access report. Does anyone have any ideas on what issues with a report
would cause the import to fail?
Thank youOn Mon, 31 Jan 2005 05:57:02 -0800, "halej51"
<halej51@.discussions.microsoft.com> wrote:
>I am getting a "Reserved Error" message when trying to import a relatively
>simple access report. Does anyone have any ideas on what issues with a report
>would cause the import to fail?
>
>Thank you
>
Strange. I imported about 40-50 reports from access, many of them
pretty complex and ugly. Yet never seen any errors...