Year End Tasks
It’s time for that annual reminder to do some system maintenance.
Make sure your backups and alerts are in place. You’re going to want to be on holiday, away from the office and the stresses found there. So, make sure your backups are working correctly. Make sure your automated processes are working. Make sure your alerts are functioning so you can relax when it’s time to be away.
While you’re at it, if you don’t have a baseline of how your system is performing, why not get some basic statistics and averages. Then when things start to feel slow, you can compare them to your baseline. This is especially helpful if your systems have extra load over the holidays.
I like to track memory usage, percentage of CPU, Disk Cache hit ratio, and buffer pool waits. You can do this using some free monitoring tools, purchase some fantastic monitoring tools, or simply use windows performance monitor and write the output to a file or a database table.
If you’re doing the later, and have some nice reporting you’d like to share, feel free to send your ideas to us by writing to btaylor@sswug.org.
DTO Feedback…
Gus Writes:
I just read through your newsletter on DTOs.
I have used the technique you described on a number of projects with success.
I will assert that the usage does not apply well to all scenarios. The applicability generally depends on the enterprise profile. A situation where there are a large number of services shared across a large number of clients can cause some maintenance headaches if not properly planned.
There is one part of the article that stands out as missing the mark a little bit. You stated that the contracts are Dot Net specific. This would be true if you use .NET specific constructs in your contracts. If you limit yourself to the simple types that support interoperability and the DTOs you define, services can be consumed by any client regardless of technology
Cheers,
Ben
$$SWYNK$$
Featured White Paper(s)
Go Beyond SCOM Monitoring with Foglight for SQL Server
read more)
Featured Script
Force SQL Error Log Switch
Force in a new SQL Error Log without restarting SQL 2K… (read more)