Hello
First post to this forum.
My question: I'm sure I read somewhere that ideally you shouldn't use the auto-increment facility in a table's id field but should generate you're own when you insert. Does this make any sense to anyone or is it just some rubbish I read online somewhere.
Any thoughts appreciated.
zing
Hi there,
Can any body please tell me how to generate autonumbering Id fields in any table.
Thanks.
Sue
Hullo!Doubt it matters too much, but I'll just start off by saying that I'm using C# ASP.NET 2.0 in Visual Studio 2005.I currently have a UID field entitled "ID", and I'd like to make it autonumbering so that users can input stuff into it through a simple web interface and not have to worry about the user's ID.Anyone know how I could go about doing this? I can't seem to find a way through VS2005's GUI, and I can't seem to find anything on the internet about doing it through an SQL statement.Thanks!
View 1 Replies View RelatedHi All,I am having trouble with a simplet INSERT statement. I want to insert a record. The field "dbid" is the primary key and should be autonumbering. What do I need to add to my code? Dim myconnection As SqlConnection
myconnection = New SqlConnection()
myconnection.ConnectionString = _
ConfigurationManager.ConnectionStrings("infoNoticeDBConnectionString").ConnectionString
Dim strSQL As String = "INSERT INTO users " & _
"(dbid, infoid) VALUES (@dbid, @infoid)"
Dim dbComm As New SqlCommand(strSQL, myconnection)
dbComm.Parameters.Add("infoid", SqlDbType.NVarChar, 50, "@infoid")
dbComm.Parameters.Add("dbid", SqlDbType.UniqueIdentifier, "dbid")
dbComm.Parameters("infoid").Value = gv2.SelectedValue
Try
myconnection.Open()
dbComm.ExecuteNonQuery()
Catch ex As Exception
Response.Write(ex.Message)
Response.End()
Finally
If myconnection.State = ConnectionState.Open Then
myconnection.Close()
End If
End Try
Response.Write("A new record has been added")
Response.End()
End Sub Thanks,
Greetings All,
I am moving from Foxpro to SQL. I am little confused
about one aspect dealing with multiple autonumbering
columns.
In foxpro it will allow you to set your fields to "autonumber"
so you can achieve having 3 or 4 fields for example with unique
numbers, depending on the application function.
When I try to do this in SQL I can setup my first identity
and PK and it autonumbers just fine, when I try to setup
a second autonumber column with a unique I cant seem to
get control of the identity to set the starting seed, Unless
I select that column in the identity to yes, but it seems to
disable the the first identity column I setup.
Can anyone tell what I missed or doing wrong ?
One last note, I am still using the Studio Manager
Still learning the programming portion..
Thanks
I created table with "id" field as "uniqueidentifier" (primary key).I connect via ODBC from MS-Acces.-->>> Don't know how to something like "Autonumber" in MS-Access.Let me know If any trigger or something like this is required.Please post some code of trigger if need.Until now I have only developed some native MS-Accessdatabases. I hope there is some solution about "Autonumbering records"in SQLServer.SqlServer 2000, Access Xp.Marek Bħbski
View 2 Replies View RelatedGents,I have come into a system that uses a secondary table to generate (forwant of a better word) Identities.egcreate table myidents( name sysname not null, ident int not null)create procedure getnextident @table sysname, @ident int outputasbeginif not exists (select top 1 1 from myidents where name = @table)insert into myidents values (@table, 0)update myidentsset @ident = ident = ident + 1where name = @tableendnow, (ignoring for now the use of reserved words) the problem is thatthis is called frequently, from other procedures. Trouble is that thecalling procedures call it from within a transaction. We now have awickedly hot spot on this table, with frequent deadlocks.Is there any relatively quick fix for this? Some locking hints orwhatever.Or do we need to go and recode, moving this kind of thing outside thetransaction (which are all rather too long for my liking), and evencosidering using identity columns as a replacement?Thanks
View 4 Replies View RelatedI've been assigned to do the data access layer for an existing SQL database created by someone else. Amazingly enough, the primary table, the one containing all of the records that are central to the db and the whole project, has over 3000 entries and no unique identifer (autonumbered ID) column. The data in all of the other columns is repetitious so none of them can be used as a primary key. I have added a column called TaskAssignmentID, designated as an int data type. The goal is to somehow autofill this column with sequential numbers and then designate that column as the primary key. (don't you just love fixing other people's mistakes?) Any suggestions/examples on how to accomplish this the easiest, most efficient way?
For reference purposes, the table is called tbl_MCHS and the newly created column is called TaskAssignmentID. The data type of the column can be changed, if that would make it easier.
Tools available include Visual Studio 2005 (very familiar) and SQL Server 2005's SQL Server Management Studio (less familiar).
Things I am restricted from doing include blowing away the table and starting over or strangling the previous developer (I asked about both). :-)
Any and all suggestions, steps, or examples will be appreciated.
Thanks,
John