It was just a thought - your old table might have had 10 columns. After the product upgrade, the table now has 20 columns, because the upgraded version stores new stuff. The suggestion that the application now uses Unicode is also a good one (that would double the size of the data).
However a 4x increase does seem very large. Cheers Ken From: Bob Fronk [mailto:[email protected]] Sent: Wednesday, 20 October 2010 12:07 AM To: NT System Admin Issues Subject: RE: SQL Query question Recreating the previous environment isn't possible due to licensing, etc. I could potentially create a SQL 2005 box and mount the old database, but this isn't my first choice for many reasons. It is quite possible that available data in the tables goes back further, but the queries are only looking at specific periods, so this part isn't any "Larger" than before. ( Example: Pulling AR data from a table for the current month. ) Are you saying that ALL the data from the table is pulled into Excel, but only the requested data is displayed? Where would the "hidden" data be? From: Ken Schaefer [mailto:[email protected]] Sent: Tuesday, October 19, 2010 12:02 PM To: NT System Admin Issues Subject: RE: SQL Query question If the application has changed, are you sure that the underlying tables haven't changed? If the tables have changed, and Excel is pulling in all data from the relevant tables, it may be possible that the tables have additional columns now, and this is resulting in increased size. Alternatively, if you can recreate the previous environment from a backup, then use SQL Profiler to see what queries are being run before/after and what data sets are being returned. Cheers Ken From: Bob Fronk [mailto:[email protected]] Sent: Tuesday, 19 October 2010 11:57 PM To: NT System Admin Issues Subject: SQL Query question Good morning list! I am by no means a SQL expert and especially not a query expert. However, I have been asked to review a problem that I believe has something to do with changing from SQL 2005 to SQL 2008R2. Brief background: The accounting system is industry specific and backend is SQL. Recent version upgrade required conversion to SQL 2008. A new SQL install to new hardware and all data migrated. Since the conversion, Excel queries of tables in the SQL database create substantially larger files than before. In one instance a query of same table(s) went from 3300kb to 131500kb. The data is the same, the queried tables are the same, but somehow the Excel file is much larger. When comparing a previous Excel file with a new one, the rows and columns are the same, the data is substantially the same. The users are using a data connector from Excel to access the tables an import the data. This process didn't change. Any DBAs out there have input? BF ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
