Good question, and one that not too many of us consider daily. We ought to make note here that DEFAULT has been deprecated in an unspecified future version of SQL...

Ah, now I understand. Then DISTINCT will be your best bet, as pointed out by GSquared, and as you've already seen for yourself.

DDL = Data Definition Language = just what you posted: the CREATE TABLE statements.

Since there is a one-to-many relationship, again, why are you doing a JOIN to derive a count?...

DDL for the tables would be helpful, along with sample data. Based on what you've provided, there is clearly a one-to-many relationship between the tables, so the question becomes, if...

Maybe, maybe not. Depends on many factors such as indexing, clustering, number of rows in the tables, etc. Check the execution plan to see what's getting processed when. Might surprise...

Did you try adding a file group to the first CREATE?

dtopicdragovic (10/11/2012)

---

Thanks for help

seems to be working.

How would you do it in the following case:

If MilestoneID = 35 Then

MilestoneDate

Else

getData()

So in our case result should...

dtopicdragovic (10/11/2012)

---

Hi!

I have a table of the following structure:

CREATE TABLE [dbo].[Doc_Milestone](

[DocMilestoneID] [int] IDENTITY(1,1) NOT NULL,

[DocID] [int] NOT NULL,

[MilestoneID] [int] NOT NULL,

[MilestoneDate] [date] NULL)

INSERT INTO [dbo].[Doc_Milestone] ([DocID],[MilestoneID],[MilestoneDate]) VALUES (30,10,'2012-10-10')

GO

INSERT INTO [dbo].[Doc_Milestone]...

Shadab Shah (10/10/2012)

---

Roland Alexander STL (10/10/2012)

---

You must drop the existing constraint and create the new constraint. Also, if the PK is the clustering key as well, you should drop or...

Jason's got it right. Look at his first post, that's the code you need.

Oops - double inserted those rows 🙂

But the idea's the same.

create table dbo.state_city (us_state char(2), city varchar(20));

insert into dbo.state_city

values

('AK',...

Looks like you want the number of rows in which (e.g.) Fairbanks appears? Then remove the DISTINCT.

You must drop the existing constraint and create the new constraint. Also, if the PK is the clustering key as well, you should drop or disable any non-clustered indexes before...

If the SP uses parameters in the WHERE or JOIN clauses, you might investigate the possibility that parameter sniffing caused a bad plan to be cached. There are many excellent...