You are aware that SQL Server Notification Services (if that is what you are refering to in your posts regarding notification services) goes away with SQL Server 2008.

Using my example tables, do you really want notes for records from on Employees, Vendors, And Customers in the same table? From a design point of view, it isn't...

I thought so. I just attacked the obvious BOOLEAN error in the original code and didn't really...

No issue. What you see in...

Let us approach it from a different direction. Three tables Customer, Vendor, Employee. Each table has a related Notes Table, CustomerNotes, VendorNotes, EmployeeNotes. Do you REALLY want...

Andrew Peterson (11/5/2008)

---

an index works as well, but try to keep it narrow and put some of the lesser values in an include. you want to keep it as narrow...

I have to agree with Lowell. Each table should have its own "Notes" table with approprate FK relationships defined.

Sounds good. Again, just curious, did you try changing the OR to AND in your original query?

Here it comes....

It Depends.

There, said it. It depends on how often the field is going to referenced in queries for one. Second, how big is the table and...

Why build an indexed view. You can just build a covering index.

--build a nonclustered index

create nonclustered index xxx_empno_IX1 on

xxx (

...

Which way did you fix your problem?

What is the view? Please post the DDL for the view as well.

Here is the skeleton code you would use:

update dbo.mytable set

column2update = somevalue

where

column2update is null;

What value you would use; that you, your developers,...

GilaMonster (11/4/2008)

---

Beats me. I'm wondering why people are so eager to throw away log records and...

Before you can set a column that currently allows NULL values to NOT ALLOW NULL values, you have to identify all the rows in the table where that column currently...