It's worst possible way.

SELECT @@Rowcount

Here is the answer on your question.

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=272895&p=1

4 different answers.

Pick the one.

Using WHERE NOT EXISTS instead of NOT IN you can check uniqueness for multiple column key.

But I really don't know what to ask to check if remote server is accessible.

Network guys use to change firewall settings without removing linked servers.

So, all my checks give me...

Absolutely!

Don't convert datetime to varchar, unless you need result as string for reporting purposes.

How you define where to start cursoring if you switch from 91-100 range to 101-110 range?

Do you do cursoring through first 100 rows?

And if you may possibly have more than 1 hour stoppage time:

declare @times TABLE (

 STOPTIME datetime,

 STARTTIME datetime)

INSERT INTO @times

SELECT '10:05:55', '10:10:55'

UNION

SELECT '10:45:55', '11:20:55'

UNION

SELECT '11:35:49', '12:49:49'

UNION

SELECT '13:49:55', '18:18:55'

declare @Numbers TABLE (

 NUMBER...

declare @times TABLE (

 STOPTIME datetime,

 STARTTIME datetime)

INSERT INTO @times

SELECT '10:05:55', '10:10:55'

UNION

SELECT '10:45:55', '11:20:55'

UNION

SELECT '11:35:49', '12:49:49'

UNION

SELECT '13:49:55', '14:18:55'

SELECT datepart(hh, STOPTIME) as HourStop, SUM(DATEDIFF(MI,STOPTIME,STARTTIME)) AS 'Downtime'

FROM (

 SELECT STOPTIME,

  Case when datepart(hh, STOPTIME) < datepart(hh,...

declare @Date datetime

select @Date = getdate()

declare @m int set @m = 8

--  @m is a number of a month you take care about. You need August - so it's 8....

Your case is easy.

You just need to run some checks before creating an index.

SELECT <List of Columns for proposed Index>

FROM <Table Name>

GROUP BY <List of Columns for proposed Index>

Having COUNT(*)...

There must be dozen of topics with the same question (and answers!) for the last couple of weeks!

NULL is not better, it's ONLY RIGHT option.

To use '0' instead of NULL you need either drop FK constraint or create dummy record with ID = '0' in 'Causes' table.

Both...

Do you have triggers on targeted tables as well?

You cannot change ANSI_NULLS settings on run time. You need to create trigger with proper ANSI_NULLS set.

Wrong.

NULL cannot be valid value.

NULL means absence of a valid value.

Never replace NULLs with default values.

Middle Name = NULL means that Middle Name for the person is not recorded (unknown).

Middle...