S
scottemick
Guest
Thanks....I think the customer's ultimate goal is to get off progress and go to SQL Server entirely, but for now my company is generating some reports for them in SSRS. I just got involved as a DBA because the programmer that's been working with them needed extra help to speed things up. I have at least 3 main choices for that we want to do. 1) Replicate the Data in SQL Server and report against that. 2) Use the progress odbc data source in SSRS 3) Use the linked servers in SQL Server to pull the data from. I was trying to go with #2 because that would be the quickest and most up-to-date data. #1 would require that I fix some of their tables up properly to have primary keys or else determining which rows need inserted, updated, and deleted gets messy. #3 works no problem if I force SQL Server in some cases to download the data to table variables and perform some of work locally like the cast to numeric for example. Here are some examples. (For the ODBC Selects I am using SqlDbx, a wonderful product). SELECT {fn replace(Netsales,',','')} Netsales FROM PUB.eDB_MajorGroupTotals T This was failing with error 7498. Amazing after I just ran dbtool option 6 and option 2, this now runs! this simple select was failing too: SELECT * FROM PUB.Entity because of a 7684 error....This now runs too! So I think I found my problem....I am on day 3 now of working with progress. I have about 15 years with MSSQL, MySQL, DB2, Access and a little Informix, FilePro, and many other db products...I had just never come across progress until now.
Continue reading...
Continue reading...