[AccessD] Access 2013 -- MDB Back Ends Dead?

Hi Mark:

If you use SPs, you get an immediate performance jump the first-time
through. After that MS SQL compiles and caches the SP and performance boost
is dramatic on subsequent requests. 

Creating Insert statements via SP is definitely not for the faint at heart.
A good days work for sure. There is code out there that will automate much
of the drudgery, leaving you to do the clean up and leave an SP that will
catch any insertion-attacks. The good news is once done its done.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Sunday, July 22, 2012 2:32 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access 2013 -- MDB Back Ends Dead?

Of course I was talking the standard ODBC connection when you connect to an
SQL Server table.

But I don't consider using stored procedures to be classified as "Access".
That's really SQL Server development ;)

I do not question that using stored procs for the inserts could be fast.
However, the implementation is a bit dirty isn't it ?
You have to iterate thru a recordset and pass each column as a parameter, no
?
I'd like to see how everyone has coded their stored procs to do these
inserts.


> Ride on, these blanket statements can be potentially  misleading. Let's
> get some specifics before we talk about horrible performance! Thank you


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com