October 18, 2015 at 4:30 am
Hi,
Hope I'm posting in the correct area.
I have a table with constantly changing data - stock.
I want to start monitoring the value of stock at the end of each month. I can do this with a simple query, export the results to Excel and store on the network.
My question is:
Are there better ways to do this with SQL Server?
I thought of a monthly "job" that does the query and outputs to a file. (Need to be able to look at each month separately though for trend monitoring.)
Then wondered, if I should have an extra table to store the data and write queries on that in the future?
Want to "keep it simple" but grateful for recommendations/suggestions of the best solution.
October 18, 2015 at 11:40 am
malcolm.garbett (10/18/2015)
Hi,Hope I'm posting in the correct area.
I have a table with constantly changing data - stock.
I want to start monitoring the value of stock at the end of each month. I can do this with a simple query, export the results to Excel and store on the network.
My question is:
Are there better ways to do this with SQL Server?
I thought of a monthly "job" that does the query and outputs to a file. (Need to be able to look at each month separately though for trend monitoring.)
Then wondered, if I should have an extra table to store the data and write queries on that in the future?
Want to "keep it simple" but grateful for recommendations/suggestions of the best solution.
I would suggest that there are better wasy than exporting to excel.
but so far all you have given us is a that you have a table called "stock"....
please provide more details.....create table scripts/sampledata and expected results.
________________________________________________________________
you can lead a user to data....but you cannot make them think
and remember....every day is a school day
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply