New to SQL Server

[NaOH]

Well from what I've done, it doesn't seem to be making it easy to access data using a Reportbuilder tool that the client has. I basically created a table for each area and another program constantly inserts data into the table whenever readings for level, flow, pressure etc change. Now, should I break down the data into smaller tables, I'm not sure what the most optimal approach is. I'm having trouble with the reportbuilder software because when I try to insert the max daily value into a cell using it in excel, it gives me the max value out of that whole table. It has a condition statement builder thing, but it doesn't seem to work for strings so I can't filter out all tagnames and leave the one I want.

Now, if I had a table for EACH reading, it'd prob work out.

Any help would be appreciated. Thanks!

 

[NaOH]

Hmm, reading up on a few things, it seems like I should be able to pull specific data out of that compiled table I have and put it into another table. Is this correct?

 

[imported_Dhaval00]

You need to specify what exactly you're using - ASP.NET, Windows Forms, SSRS, Crystal Reports, etc. Also, elaborate a bit on your design so that the DB folks here can understand your dilemma.

 

[NaOH]

ReportBuilder Text
RSSql to move data from process computers to SQL server

My design is pretty straight forward as of now. Tables for each area of the plant. Columns for the time/date, tagname, value, valuetype, and Subarea.

RSSql scans for changes in the values every 10 seconds and inserts it into the corresponding table if it's different. All types of data is stored on the same table. So when I use reportbuilder, I want to be able to insert into an excel cell, the max,min,avg,etc in a cell for a specific tagname.

I think reportbuilder should be able to do this on it's own, but I'm trying to figure it out. I'm not on site right now so I'm just doing my research. I already contacted the cust. support. They told me that I needed to configure reportbuilder differently for my type of sql table structure. I'll give it a shot tonight, but I was wondering if I was shooting myself in the foot by structuring my tables this way.

 

[Markbnj]

I would usually say normalize the tables. In this case maybe it depends on where you need the best performance. The way you're doing it now probably results in faster inserts, and if you're collecting a lot of samples that might be important. On the other side it will make the aggregate queries your reports need slower and more complicated. It might also prove less flexible in the long term.