Features in 2005

I've heard that new various 2005 features talked about, but when I look at
the 2005 SQL Lab, I see none of them: specifically a calendar control, pivot
tables, custom controls, etc. in the BI Development tool.
http://msdn.microsoft.com/sql/2005/2005labs/default.aspx
Is this because the new version of dev environment is not integrated
yet...or have these discussed features been dropped?If you download the Books Online for September CTP,
http://www.microsoft.com/downloads/details.aspx?FamilyID=F0D182C1-C3AA-4CAC-B45C-BD15D9B072B7&displaylang=en,
and navigate to the Reporting Services Enhancements section you will
get a pretty complete description of what's new or improved in
Reporting Services 2005.
Andrew Watt
MVP - InfoPath
On Tue, 11 Oct 2005 14:07:02 -0700, "Billg_sd"
<Billgsd@.discussions.microsoft.com> wrote:
>I've heard that new various 2005 features talked about, but when I look at
>the 2005 SQL Lab, I see none of them: specifically a calendar control, pivot
>tables, custom controls, etc. in the BI Development tool.
> http://msdn.microsoft.com/sql/2005/2005labs/default.aspx
>Is this because the new version of dev environment is not integrated
>yet...or have these discussed features been dropped?sql

fastest way to do large amounts of updates

I was wondering what is the fastest way to UPDATE lots of recods. I heard the fastest way to perform lots of inserts in to use SqlCeResultSet. Would this also be the fastest way to update already existing records? If so, is this the fastest way to do that:

1. Create a SqlCeCommand object.
2. Set the CommandText to select the datat I want to update
3. Call the command object's ExecuteResultSet method to create a SqlCeResultSet object
4. Call the result set object's Read method to advance to the next record
5. Use the result set object to update the values using the SqlCeResultSet.SetValue method and the Update method.
6. repeat steps 4 and 5

Also I was wondering do call the SqlCeResultSet.Update method once per row, or just once? Also would it be possible and faster to wrap all that in a transaction?

Would parameterized updates be faster?
Any help will be appreciated.
To answer some of my own questions, for an SqlCeResultSet object, you must call the Update function once per row. Also you can wrap it in a transaction, but that will probably slow the process down, although this may still be a good idea.

My main question still remains unanswerd: What is the fastest way to do large amounts of updates? I will be running some tests soon and will post my results here.
|||

Some things you can do to improve update performance:

1. make your update statement a parameterized query, prepare it, and reuse it for each update, changing only the parameter values

2. keep indexes on the table to a minimum (or even remove them in extreme cases - then readd them after the updates complete)

3. SqlCeResultSet is the fastest mechanism if ou are using CF2 and SQL Mobile - yes, you call update on each row

-Darren