Hi John,

from a business viewpoint the format that you use to transfer the data is not really that important, given that you ensure that the data are protected and do not  leak during the transfer.  Now, from a technical viewpoint, if all you are trying to do is to to "migrate" data....either CSV or XML should be fine.  I'd say..just use whatever  is most convenient.  I'd use XML only if you'd be planning to make the data more readily available to 3rd parties/systems.

Naturally I am generalising here, as I am not aware of the exact circumnstances, but I hope the above help.

regards,

Denis
www.naxtech.com

Hello John,

I think your database supplier is on the right track here - if they can support CSV files then your web agency should have no issue in ceating output files in that format.

If you have plans to make this data available to others (highly unlikely given the nature of the data you are describing!) or wanted a more generic format then there might be a case for thinking about using XML . But to be honest, in your situation I can't help thinking that there would be no benefit what so ever.

Re 'what are the issues in using CSV', none in the case you describe. XML would be a different layout for the file, but I can't see that it would be better.

In fact if your database supplier doesn't support it then it all becomes irrelevant anyway really :-)

Kind Regards

Ed

http://www.n3wmedia.com

On 15:32:20 22 September 2008 danielb wrote:

hiya, John,

as Denis says - can't see any difference between XML & CSV if you've described all the requirements. Has your agency said what they feel the advantage would be?

daniel

Hi Daniel, I was meeting with an agency which is pitching for the website and we were talking about the transfer process of data from the website into the database.  So I shall wait and see when they do a full pitch after they have talked to the database provider.... I may well see a double pitch for the database as well!

thanks

John

Advanced scheduling - xSQL Profiler provides a powerful scheduling utility that allows the user to define multiple intervals during which the trace should be running on the selected servers. Those intervals can be scheduled to occur only once or recur every day, week or month.Flexible reporting interface - the view trace data capability allows you to filter the data based on event type, server, database, user, datetime, text of the event. You can further group the data based on any of the displayed columns by simply dragging and dropping a column header. In addition, xSQL Profiler gives the user the ultimate power by providing for direct querying of the xSQL Profiler database
Use for performance, auditing and compliance - the flexibility of xSQL Profiler makes it an ideal tool to use for pinpointing SQL Server performance issues, auditing certain events and ensuring that you are in compliance with different sets of regulations such as Sarbanes-Oxley, HIPAA, GLBA, etc.

geovani

www.drivenwide.com

Nowadays, Web Services (WSs) play an increasingly important role in Web data management solutions, since they offer a practical solution for accessing and manipulating data sources spanning administrative domains. Nevertheless, they are notoriously slow and transferring large data volumes across WSs becomes the main bottleneck in such WS-based applications. This paper deals with the problem of minimizing at runtime, in a self-managing way, the datatransfer cost of a WS encapsulating a data source. To reducethe transfer cost, the data volume is typically divided intoblocks. In this case, response time exhibits a quadratic-like, non-linear behavior with regards to the block size; as such, minimizing the transfer cost entails finding the optimum block size.
---------
Tanyaa
www.drivenwide.com