I do not understand you fully. Are you suggesting I use SQL Server for that single table, while the rest of the app uses DBF's? Or what?
El 22/04/2010 11:11, Stephen Russell escribió: > For doing HIGH volume transactions this may fit the bill just fine. I > know that this will handle 10,000 rows per hour no problem in a single > table. That from experience. Other who have done super high volume > on line apps say that is pathetic only 3 inserts per second. They > brag of 300-1000 per second for an ebay clone. > > So you can get a Free version of SQL Server. You ask it to insert a > row and give you back the value of the key. That will be faster then > a large multi-user operation that has to do a table lock / row lock > type of operation with other users hitting and banging to get in. > > > > ------------- > On Thu, Apr 22, 2010 at 8:39 AM, Rafael Copquin<[email protected]> > wrote: > >> Thanks Stephen >> >> I am not using SQL Server for this app, but will keep this code for >> reference. >> >> >> El 22/04/2010 10:30, Stephen Russell escribió: >> >>> On Wed, Apr 21, 2010 at 3:29 PM, Rafael Copquin<[email protected]> >>> wrote: >>> ---------------------- >>> >>> Would you consider a SQL Server that has a table for this need. Only >>> one column, the key you need. Below is code to create a table a SP to >>> populate it and it will return the KEY # back to you. >>> >>> CREATE TABLE MyTable >>> ( >>> MyPK int NOT NULL IDENTITY(1,1) >>> CONSTRAINT PK_MyTable PRIMARY KEY, >>> MyData int NOT NULL >>> ) >>> GO >>> >>> CREATE PROC MyProc >>> @MyData int >>> AS >>> SET NOCOUNT ON >>> INSERT INTO MyTable (MyData) VALUES(1) >>> SELECT SCOPE_IDENTITY() >>> GO >>> >>> EXEC MyProc @MyData = 1 >>> GO >>> >>> I don't think that you could grow the 4 gig FREE version in a year >>> with transaction rates in the thousand per hour. You will have to >>> truncate the log file but that is a maintenance process that is easy >>> to implement. >>> >>> Just tossing out an idea for you. >>> >>> If your transaction rate if 10,000 per hour or more you will need to >>> delete some of this data in your maintenance plan and that is real >>> simple as well. >>> >>> Select top 5 * >>> into #t1 >>> from MyData >>> order by MyPk desc. >>> >>> Declare @min int >>> >>> set @min = (select min(MyPk) from #t1) >>> >>> Delete from myData where myPk<= @min >>> >>> >>> >>> >>> >>> >> >> --- StripMime Report -- processed MIME parts --- >> multipart/alternative >> text/plain (text body -- kept) >> text/html >> --- >> >> [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
