Developer Day en Español!!

Hi guys,

CodeGear is hosting "Developer Days en Español" a nice gathering of great developers with the spanish speaking Delphi community.

There is a wide variety of sessions including Delphi, Interbase, PHP and Java.

It is only for 2 days, today was the first session and it was great. An average of 300+ guys were listening online to the different sessions, in my opinion a great success.

So if you want to check it out, this is the website.

Enjoy!

A nice surprise on Delpih 2007...

I was creating a "Lost Connection" dialog box for our rich client applications and as a distraction I was browsing around through thousands of nice icons on the internet, when I finally selected the icon that i wanted, I realized that it was (as almost every nice icon now days) a .png file.

Big disappointment I said, cause my mighty Delphi doesn't support that in a native way, I need to use a open source component, (actually there are tons of them, but I don't have the time for that) so I will have to convert it to that ugly bitmap thing. Oh well, i did and when I was getting ready to upload the image, sweet surprise!

TImage supports now gifs, cur, pcx, ani, png, gif, jpg, jpeg, bmp, ico, emf, wmf. I don't know if that is something new, but for sure it wasn't on Delphi 7 :P.


Love my D2007.

Visual Studio launch in 2008....

Latest news said that Visual Studio will see the light in a joint launch with MSSQL Server 2008 and Windows Server 2008 in Los Angeles on February 27th, 2008.

But, it will be released officially by the end of this year.

CodeGear Studio will be out around September.

Database scalability with MSSQL 2005

Some news from the battlefront...

We are expecting at least a 75% increase of our internet traffic, db transactions, network and database activity in general so our entire company is working hard on getting ready to manage this incoming wave.

Regrettably, life is not always good and the core of the business is setup around a system using a typical client/server architecture where each workstation creates a connection to the database and to make it worst, establishes server side cursors to fetch all data they need.

Now on the other hand, the website is driven by old school ASP pages, using adHoc Queries or direct stored procedure calls to the already beat up database. Finally, it is important to mention that this is running on ODBC connections.

End result?, chaos, in high traffic moments the entire network slows down and all the applications switch to a slow silent death walk to a total IT crisis. There is no caching techniques, no business layer, basically no middle tier... all the opposite things to what I'm used to deal with, and that is why it is my mission to turn this around and take over the world. (moooooahahaha)

Well, the mission is simple, we can't change much in short time, so we need to make this system work as good as possible. So, my first task is to provide a list of recommendations towards the deployment of our new database servers running MSSQL 2005.

Yup, we are migrating from MSSQL 2000 to MSSQL 2005, people will think that it is a simply straight import/export, but special considerations need to be made when dealing with the databases collation which has completly change from one version to the other one and to the famous "compatibility modes". Keeping an imported database in Compatibility mode 80 (MSSQL 2000) may save you headaches but will offer you little in terms of all the good new toys and performance tricks that you can apply on compatibility mode 90 (MSSQL 2005).

Bellow is a summary of my initial recommendations aimed to the physical database storage design aspect that you should follow when dealing with a situation like the described above:

1. Server side cursors implies lots of memory usage on the database. So, increase memory on the database server, the more the better. Make sure your database is using it, by checking the database memory limit. (special attention to the 3gb limit on the non Enterprise versions of MSSQL)
2. Multiple core machine? well, you will not use them if you don't separate that big nasty .mdf file into multiple .ndfs, what is the recipe? the number of data files within a single file group should equal the number of CPU cores.
3. For optimized I/O parallelism, use 64 Kb or 25 Kb strip size when defining the RAID configuration.
4. Use manual file growth database options. Automatic is only for development (ja! you didn't knowt that did ya?)
5. Increased size of “tempdb” and monitor space usage, adjusting accordingly. The recommended level of available space is 20%. All your temp tables and indexes are created there so, keep that guy with enough space, if you are using the default size that is only 8MB, and that is basically 8 floppies, so be nice, put some more space there.

Alright, so that should buy us some time to concentrate on the next stage, database optimizations. Until the next post.

CodeGear drops C# Builder.

I was listening to one of the weekly community podcasts from CodeGear, and one of the topics that was mentioned was the announcement of C# Builder being dropped from the CodeGear Developer Studio 2007, to be released later this year.

Winforms seems to be a no no too. It seems they will be putting all their efforts on Delphi and C++ and Delphi.Net using the VCL.Net. They will convert their existing support for C# Builder to the same level of the VB personality, which means edit, syntax highlight, compile, and basic
debug functionality.

It looks like we will have the possibility to use any existing C# component and add it to your Delphi.Net project with no problem.

For people using ECO with Winforms, they will be ways to move into the direction of VCL.Net, which will be fully supported by ECO on the coming Delphi.Net release.

I certainly agree with their moves, there is no point on supporting a language that they cant controlled. They can use the .Net framework or the Win32/Win64 native APIs, but just like they did with Win32 by building the impressive VCL on top of it, expanding the VCL to support .net will also forced the VCL under native APIs to be extended to new cool functionalities.

Lots of news around CodeGear, which just reasures my thoughts towards the fact that these guys are doing the best they can to have things going the proper way.

Oh final comment, initially it was mentioned that Generics will be only supported from a consumption level, that seems not to be the case, production of Generics will be there too. But, only for .Net initially.

ASP.Net not too scalable....

Scalability is a daily concern on my business. We managed thousands of requests, that startup lots of transactions that will make any online bank website simply jealous.

A couple of times, I worked with companies that use ASP.Net as their web framework of preference and it was not long when we start having scalability problems. It is a well known issue with ASP.Net, but there are solutions.

I found this interesting article that talks about the issue and gives a good solution.

Read it!

Using Visual Studio 05...

Yes, I know, but hey, I was programming on Java a couple of days ago, so for me it is just more stuff to learn and at least it is more visual than Java.

I'm in no way leaving behind my sexy Delphi, we just got a new update and a cool roadmap, but, I need to develop some web applications that connect to my Delphi middletier and the option I have right now is to do some ASPX on C#.

If I'm lucky enough, I should have the new Code Gear Developer Studio with support for .Net 2.0/3.0 by September, so I can use it.

The big reunion.

Hi guys,

I don't know if you were aware of this great reunion between the last two old schoolers of the software industry: Bill Gates and Steve Jobs, on an interesting chat together at D5!!.

The vision they had and have is simply outstanding, the advances we enjoy today on the software area can be easily blame to these two great minds.

Enjoy!

http://d5.allthingsd.com/20070530/video-steve-jobs-and-bill-gates-prologue/

What will many cores mean to future window releases?

This is a good article about what is going on with Microsoft around the new trend on Multi Core devlopment.

You got to love AMD Opterons :)

Faster web pages...

This is the link of an outstanding presentation made by the Yahoo’s “Exceptional Performance Team” about optimizing website performance by addressing front end issues. This is part of the web 2.0 expo that happened last April. A MUST read.


Enjoy,


http://www.web2expo.com/presentations/webex2007/souders_steve.ppt

Yes, it is a power point presentation.

A great option for middletier development!

For all those developers that are looking for another option to the mighty DataSnap, now there is a great opportunity to develop reliable and scalable middletier solutions for the same price.

Components4Developers is offering their popular middletier software for free. What is the deal?

Simple, register and download. TurboMiddletier is a full version of their enterprise middletier software KbmMW (a couple of transport protocols and channels are removed but nothing major), it only supports the latest Delphi version, so, if you have Delphi 2007 go and get it now!!

I personally use Data Snap, RemObjects and KbmMW in our projects and can only say good things about them. I do admit that KbmMW is a more mature framework with lots more functionality, but on RemObjects SDK favor, they offer a great DataSnap integration pack that help companies using DataSnap to migrate to their SDK.

Whatever you pick, you will be on good hands, in the meanwhile go and get that!

Using Agile methodologies on your favorite IDE.

My current job is moving towards an Agile development, so, in order to be one step ahead of the game, I am implementing on my home projects most of the methodologies that we will or should be using in our everyday development life.

Browsing around I found this site, which basically is dedicated to implementing Agile methodologies in Delphi. Take a look at it, and subscribe to the forum, it promises to be a great source of knowledge for all those XP/SCRUM/Agile fans.

Ajax and Delphi

I'm finally working on the web applications of my home project, and I decided to work with Intraweb 9 as my web framework which now supports "Ajax" events on most of its components and comes built-in my brand new shinny Delphi 2007.

But, browsing around I found a set of extremely interesting examples and articles about using the Microsoft flavor of Ajax (Atlas 2.0) on ASP.Net with Delphi.

Take your time on rewiewing these examples from Steve Trefethen.


It is worth to mention that TmsSoftware replied to my question about possible updates to their Intraweb web components, the answer YES!, so lets wait a couple of days, for the goodies to come.

Delphi Developer job offer in NJ?

I saw this add from "The Lair of the Pythia" blog, so I will help spreading the word.

Delphi Job opening here!

So go there and make us all proud!

The Phone interview process...

Well,

One of the different roles that job after job I've done is interviewing new candidates for my team.

I'm very comfortable with the one-on-one, mano a mano model of interviewing, but most recently I'm dealing with a new cool variant of it, the phone screening, why is it new? well, usually that kind of process is managed by the HR people, but now days, based on the offer/demand sometimes is healthy to screen a guy before he even puts a foot out of his home.

Oh God, yes, distortion on the communication line, language barriers, unable to read body language, unable to picture your world into mine, unable to cross that border of understanding and agreement, indeed, it is a bit more difficult than my original play field.

I know that practice will make the difference for me, but also, I was lucky enough to get this link from a co-worker that it is going through the same process.

READ IT! if your duties involved phone screening, it may help you to understand the situation and save you from the confusion we noobs need to go through at the beginning.

Code Rage 2007!!! NOW!!

Guys, more than 20 online conferences covering from powerful Delphi to Java, Ruby, Php, Interbase and lots more!

Its free, its cool and its from the best developer tools company WHAT ELSE YOU WANT!!!

GO HERE NOW AND REGISTER! Starts today March 12th! 6:30AM PST!!

10 basic principles of SOA

Lately, all my work is around implementing solutions following a SOA approach. After working for several years with multiple software vendors on my industry, and having to deal with endless integrations, I'm ending up aiming my tools and goals to it.

This is a nice little article about 10 things to consider while following a SOA mentality.

The ADO prepared property.

Today I was playing with some ADO queries and I stumble one more time with the famous prepared property. Based on the BDS help it says:

Description Set Prepared before calling the Open method to specify whether ADO prepares the command used to create the dataset’s recordset. If Prepared is set to true and the dataset component is connected to a data store, ADO prepares the command before executing it. If Prepared is set to false, ADO does not prepare the command. The default value of Prepared is false.

Now, after a bit of research I found this interesting article on the msn dev network.

The important part is here:

Prepared property

In theory, the Prepared property was designed to reduce work on the server by pre-compiling ad hoc queries so subsequent executions would use a temporary stored procedure instead of repeating the compile phase each time the query is executed. However, this is not the case with ADO's implementation—keep reading.

Since ODBC was invented some years ago, SQL Server has gotten much smarter—it now knows how to leverage existing (in cache) compiled query plans. That is, once you execute a query from ADO (or by any means), SQL Server constructs a query plan, saves it in the procedure cache, and executes it. When the query is done, SQL Server marks the query plan as "discardable" but leaves it in memory as long as it can. When another identical (or close-enough) query comes in, which is very likely in systems running multiple clients, SQL Server simply re-uses the cached plan. This saves a significant amount of time and greatly improves scalability. It makes SQL Server actually run faster as more users are added, assuming they're doing about the same things with the same set of queries.

ADO and its ODBC and OLE DB data providers know about this strategy, and in most cases they execute sp_executesql to take advantage of this feature. However, this puts the Prepared property in a quandary. It insists on creating temporary stored procedures, but the data providers insist on using sp_executesql. The result? Chaos. I describe what happens a little later when executing Command objects is discussed.

My recommendation for the Prepared property: forget it—at least for SQL Server. For other providers, set up a trace that shows exactly what's going on—what the server is being asked to do.

Now this is extremely interesting for me, specially the sp_executesql part, DataSnap indeed wraps every call in a "sp_executesql" so we are good there, now about using the prepared property, I will do more research on it, but for now, I will leave it alone. :P

Code Rage 2007!!!

Go to the virtual conference from CodeGear called CodeRage 2007.

It includes Delphi, Java, Php and even Ruby sessions with an All-Star set of speakers.

For more information go here!

Now, I think that everybody knows about it, but just in case...



Delphi 2007 for Win32 is available now! and in a well expected move, the new Delphi for Php makes his debut. A visual IDE for PHP using the same VCL structure that we all know and learn to love.

More Delphi News!!

Wow the information is in pieces everywhere.. check the following segments of "information" said by Michael Swindell (Delphi VP - CodeGear) that appeared on the borland newgroups:

"
c) Delphi Product line - we are realigning development plans and approaches
to focus on the individual native code Win32 editions (Pro/Ent) of the
products first, then fold them into an updated Studio that will include the
.NET updates. Architect and Turbo's would fall out of the Studio releases.
The Turbo's eds will become more lightweight in the process as well. The
majority of Delphi (and C++Builder) developers are focused on native code
development - so we are aligning our releases and timeframes accordingly.
Moving everything into monolithic Studio releases had some positive effects
but also some drawbacks that came thru in customer feedback. Having to wait
for the "all personalities" was not ideal for C++ and Delphi native
developers, who had either no or minimal interest or need for .NET. It
spread attention more thinly across the products, so we are changing the
approach so that during the year Delphi native developers have focused
specific attention in a product release, same with C++ developers, and .NET
developers. This approach actually worked quite well in past lives with
Delphi and C++Builder - although the complaint years ago from C++Builder
developers was that they had to wait 6mo to a year for the latest Delphi
features... which is something that we aim not to fall into. "

Then in addtion pay attention to the new "ALL DELPHI" intention with the new pricing model and SKU's:

"
Turbo Delphi Explorer -> Turbo Delphi "better" -> Delphi Pro -> Delphi Ent

same as above for C++

then Studio Pro/Ent/Arch incl both C++ and Delphi and .NET and Win32

Turbo Pro New and Delphi Pro Upgrades similar price level. So it will be
recommended in order to keep the feature level go to Delphi Pro as the
upgrade. This is a tuning of the editions. We released the Turbos with the
intention that we would see what worked and what didn't and make some
changes in 2007 to improve.

> How is this going to be handled?
> Or is the "lightweight" reference to reduced resource demands rather
> than reduced features?

lighter weight - in features and resource and download image

in general we have 12yrs of sku's editions pricing for Win32, .NET, Pascal,
C++, Linux, and more to work out the best "model" that cleans things up, and
focuses our energy (development, packaging, and marketing) on the things
that are most important to existing customers and enables us to put Delphi
into more developers hands than ever. So there will be some things that we
do that will seem like we're undoing something we've done or said
previously, or changing a position on something previously stated or
published. Some things will probably seem crazy or sacrilege, but we plan to
grow Delphi, and to do that requires a little bit of house cleaning and
tuning. We'll probably make a few mistakes in the process, but the goal is
long term. Delphi and C++Builder have helped millions of developers, we
think the Delphi way of developing can benefit millions more developers -
and we want to bring the Delphi ideas and approach to everyone we can. The
CodeGear difference is that we're going to take some risks and try new
things, but we won't be doing it at the expense of our customers. "

It is expected a Delphi release by the end of March maximum!.