Completely different I would say, have a table with MeterId, Time and MeasuredValue. You will (over time) get lots of rows, but with proper indexing for your queries this should...

Thanks for the response folks. You're absolutely right, having an indexed XML column will greatly improve the statistics, and generate a more efficient execution plan, using merge joins instead of...

First of all, do yourself a favor. Use correct name, do not alter the names when you post. It is a mere mess to decipher your code trying to understand...

If you think for CLR datatype, I'd say definitely not. You would add quite a bit of overhead. CRL Datatypes may be great when you need complex validation, but not...

To a bunch of users? I'd say no, it is not a good idea. Do you really have a bunch of users that are capable of understanding execution plans? Furthermore,...

logicinside22 (10/28/2011)

---

Hi Guys,

I want to know how i can get list of all SQL Server installed in different IT Enviornment ( Dev,Test,Prod)?

Any 3rd party tool or...

Pardon me for asking, but why is this posted as a poll?

No pun intended, actually it is your request that is meaningless. What you want, is the server to be able to impersonate each and every user account so that it...

First thing to come into my mind: Do you have multiple instances on the server? If so, you should be aware of the fact that max server memory is a...

JonFox (10/27/2011)

---

Index fragmentation shouldn't have an impact on whether the query optimizer chooses a scan over a seek; the optimizer tries to minimize reads when choosing a query plan, but...

If I understand your issue right, this is due to data being flushed out of the buffer cache. This is actually quite normal if you update statistics or rebuild indexes...

My Seek operator executed approximately 32000 times, fetching one row each time. It still showed up as a single seek in sys.dm_db_index_usage_stats.

First of all, a white paper on plan caching.

What you may have experienced is a sub-optimal execution plan being cached. The first time a query is executed, the execution plan...

Seems like the query for some kind of reporting. Although I don't like it all that much, I tend to end up with dynamic sql in such cases:

declare

One of two options comes into my mind:

* Dynamic SQL

* Convert to left outer join instead, and use case statement to select from either of these two with a proper...