Not too bad at all, it definately covered the normal user requirements
Unfortunately our system is growing at geometiric rates (was 10GB a week last year), now 20, with occasional blips up to 40-50GB.
It's a little worrying when you buy an extra 4TB of storage and expect to have to get more by christmas next year, but at the same time it's also exciting, which is why i still love this job so many years into it.
Thanks for the responce, firthr. I would love to research on your mentioned topic and see whether I could get something to write on. Thanks for your input
~Arindam.
Thanks for the responce! You are exactly right in your opinion. Certainly we could find out new rules and formulae, but every problem comes out to be a new one
I love this job too. Hope you could cope up with the geometrical growth!
Yep, we're coping quite well, our SAN is more than up to the job so long as we keep adding extra storage and partitioning the data properly.
I might get round to writing an article on what we did in the hopes that it helps others, but it might be a while as I'm currently way too busy
I will be eagerly waiting to see something on that
Write your experience and how you came up with a solution. That will be interesting.
I'd call this "Disk Management 101", in that it covers the basics. I'd say the majority of the people in this forum already have implementation plans for storage capacity planning. I was personally really hoping to see more about External Capacity... can we expect one of those in the future, too?
Given the above, SQL Profiler, and a good trace template, I have found it quite easy to point out Internal (SQL-object based) performance problems. But what about those problems not associated with I/O? Is it a Network Problem? Client problem? I have theories about the problems that I have encountered over the years (like if MS Access is running a query and the CPU is pegged, then leave me alone ), but what if it isn't Access? How do you work with your network team to find the problem?
I am a firm believer that network n0mes don't exist.
