Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2002-01-23 : 08:35:34
|
| Michael writes "We have 4 automated assembly lines which produce a lot of data from the quality test results. Each line stores its data on its own Dell server computer running MS SQL Server 2000. The system generates about 84 megs of data on each server daily. There are 17 tables of test results that are joined in different combinations to store the results for the 8 different part types. The part types are the same on each server.QUESTION: How do we merge all this data together for an ADO component?We use Infragistics Ultragrid (ADO Component) to display the data based on user selected ranges (date, part type, etc.) with an ADO recordset and SHAPE and JOIN commands. This works fine for data on one server, but does not work across all of the servers at once. Parts can be run down multiple lines. QA people have to go to each line to get the results for their reports.The VB application does talk with each server for individual results (1 part), but not for multiple parts supplying the ADO component.Any pointers in the right direction would be greatly appreciated. I've got to much data on my hands! Thank you in advance.Michael Shepardclearly@idirect.com(905) 438-0015" |
|
|
Nazim
A custom title
1408 Posts |
Posted - 2002-01-23 : 08:51:43
|
| How About creating linked server at one place , joining them in a stored procedure and calling it thru ADO.--------------------------------------------------------------Dont Tell God how big your Problem is , Tell the Problem how Big your God is |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-01-23 : 12:56:13
|
| I think a better solution would be to create another server, and replicate all the data to the central server. Then run your reporting off of that one server.-Chad |
 |
|
|
|
|
|