I have a sales table( id, date , techid, amount)
id date techid amount
---
1 01/01/2005 tsmith 99.99
...
1054 08/16/2005 jborrow 29.99
I need to create historical report&graph with monthly totals (amount) for
every agent: Jan,Feb...Aug.
Jan Feb... Aug
tsmith 15898.44 69352.88 586311.55
How can I aggregate daily data in order to get historical
monthly/weekly/daily totals breakdown.
Is there any function or option (in Report designer)?
Thank you!You may want to read up on "grouping" in the RS Books Online and also look
at the "Company Sales" and the "Employee Sales Summary" sample reports of RS
2000.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"agenda9533" <agenda9533@.discussions.microsoft.com> wrote in message
news:4C7B3EAA-7FAC-400F-A80F-9586A4A1EFF1@.microsoft.com...
>I have a sales table( id, date , techid, amount)
> id date techid amount
> ---
> 1 01/01/2005 tsmith 99.99
> ...
> 1054 08/16/2005 jborrow 29.99
> I need to create historical report&graph with monthly totals (amount) for
> every agent: Jan,Feb...Aug.
> Jan Feb... Aug
> tsmith 15898.44 69352.88 586311.55
>
> How can I aggregate daily data in order to get historical
> monthly/weekly/daily totals breakdown.
> Is there any function or option (in Report designer)?
> Thank you!
>sql
Showing posts with label amount. Show all posts
Showing posts with label amount. Show all posts
Monday, March 26, 2012
Friday, March 9, 2012
High availability at subscribers using database mirroring
I have a mirrored database with transactional replication publishing
to 2 databases on different servers.
The amount of data written to the principal is fairly low.
The requirement is that at least one of the subscribers must be
available at all times with a latency of no greater than five minutes.
I thus have redundancy at the publisher via mirroring and at the
subscribers via multiple databases containing the same data, but I
can't see how to achieve redundancy at the distributor, since the
distribution database cannot be mirrored.
What is the recommended method of making the distributor highly
available? At this site there is reluctance to pursue SQL clustering
and to rename servers as described in BOL. At the moment it looks like
a need a set of scripts to completely set up replication from scratch
if the machine where the distributor DB lives goes offline.
Or, will Katmai offer new features to make all of the replication
components as highly available as the publisher can now be via
mirroring?
Hi Garry,
I understand that you would like to implement a high availability SQL
Server replication. You implemented Database mirroring for your principal
server and multiple databases with same data at the subscribers, but you
would like to know how to implement redundancy at the distributor since the
distribution database cannot be mirrored.
If I have misunderstood, please let me know.
I recommend that you can create a failover cluster for your distributer.
Deploy the distribution database to the virtual server instance. Also, for
your scenario, I think that it is better to use failover cluster for your
publisher since it just need two servers, but to implement a high
availability database mirroring, it needs three servers, principal server,
witness server and mirror server.
For how to setup a SQL Server 2005 failover cluster, you may refer to:
How to: Create a New SQL Server 2005 Failover Cluster (Setup)
http://msdn2.microsoft.com/en-us/library/ms179530.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
to 2 databases on different servers.
The amount of data written to the principal is fairly low.
The requirement is that at least one of the subscribers must be
available at all times with a latency of no greater than five minutes.
I thus have redundancy at the publisher via mirroring and at the
subscribers via multiple databases containing the same data, but I
can't see how to achieve redundancy at the distributor, since the
distribution database cannot be mirrored.
What is the recommended method of making the distributor highly
available? At this site there is reluctance to pursue SQL clustering
and to rename servers as described in BOL. At the moment it looks like
a need a set of scripts to completely set up replication from scratch
if the machine where the distributor DB lives goes offline.
Or, will Katmai offer new features to make all of the replication
components as highly available as the publisher can now be via
mirroring?
Hi Garry,
I understand that you would like to implement a high availability SQL
Server replication. You implemented Database mirroring for your principal
server and multiple databases with same data at the subscribers, but you
would like to know how to implement redundancy at the distributor since the
distribution database cannot be mirrored.
If I have misunderstood, please let me know.
I recommend that you can create a failover cluster for your distributer.
Deploy the distribution database to the virtual server instance. Also, for
your scenario, I think that it is better to use failover cluster for your
publisher since it just need two servers, but to implement a high
availability database mirroring, it needs three servers, principal server,
witness server and mirror server.
For how to setup a SQL Server 2005 failover cluster, you may refer to:
How to: Create a New SQL Server 2005 Failover Cluster (Setup)
http://msdn2.microsoft.com/en-us/library/ms179530.aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
High amount of Full Table or Full Index Scan
Hello
The Installation is SQL Server 2005 Enterprise Edition with 8 Processor.
With permon and the performance counter "SQLServer:Access Methods\Full
Scans/sec" i monitor the value 80 -180. Every time these values are there
the 8 CPU have a workload of 80 Percent in Total. With the SQL Server
Profiler i found the Query who made the Full Table/Index Scans over table's
with 8 Million rows.
So now i have to proof that these full table/index scan are the cause of the
high CPU Workload and the bad performance.
How can i use the DMV View's to analyze which "Select" are really causing
Full Table/Index scan ath the Moment. Are there tools that i can use for
these analyze ?
regards
PaoloProfiler is probably best for that task. If it is a sproc causing the big
reads you can either review the code and figure it out yourself (using
profile-captured input parameters for the sproc). You could also step down
to statement level tracing inside the sproc call, but be warned that this
can lead to significant performance hit for the profiler data.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Paolo Taverna" <nomail@.nomail.nml> wrote in message
news:Oe%23mzuCgIHA.3940@.TK2MSFTNGP05.phx.gbl...
> Hello
> The Installation is SQL Server 2005 Enterprise Edition with 8 Processor.
> With permon and the performance counter "SQLServer:Access Methods\Full
> Scans/sec" i monitor the value 80 -180. Every time these values are there
> the 8 CPU have a workload of 80 Percent in Total. With the SQL Server
> Profiler i found the Query who made the Full Table/Index Scans over
> table's with 8 Million rows.
> So now i have to proof that these full table/index scan are the cause of
> the high CPU Workload and the bad performance.
> How can i use the DMV View's to analyze which "Select" are really causing
> Full Table/Index scan ath the Moment. Are there tools that i can use for
> these analyze ?
> regards
> Paolo
>
The Installation is SQL Server 2005 Enterprise Edition with 8 Processor.
With permon and the performance counter "SQLServer:Access Methods\Full
Scans/sec" i monitor the value 80 -180. Every time these values are there
the 8 CPU have a workload of 80 Percent in Total. With the SQL Server
Profiler i found the Query who made the Full Table/Index Scans over table's
with 8 Million rows.
So now i have to proof that these full table/index scan are the cause of the
high CPU Workload and the bad performance.
How can i use the DMV View's to analyze which "Select" are really causing
Full Table/Index scan ath the Moment. Are there tools that i can use for
these analyze ?
regards
PaoloProfiler is probably best for that task. If it is a sproc causing the big
reads you can either review the code and figure it out yourself (using
profile-captured input parameters for the sproc). You could also step down
to statement level tracing inside the sproc call, but be warned that this
can lead to significant performance hit for the profiler data.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Paolo Taverna" <nomail@.nomail.nml> wrote in message
news:Oe%23mzuCgIHA.3940@.TK2MSFTNGP05.phx.gbl...
> Hello
> The Installation is SQL Server 2005 Enterprise Edition with 8 Processor.
> With permon and the performance counter "SQLServer:Access Methods\Full
> Scans/sec" i monitor the value 80 -180. Every time these values are there
> the 8 CPU have a workload of 80 Percent in Total. With the SQL Server
> Profiler i found the Query who made the Full Table/Index Scans over
> table's with 8 Million rows.
> So now i have to proof that these full table/index scan are the cause of
> the high CPU Workload and the bad performance.
> How can i use the DMV View's to analyze which "Select" are really causing
> Full Table/Index scan ath the Moment. Are there tools that i can use for
> these analyze ?
> regards
> Paolo
>
Subscribe to:
Posts (Atom)