Well, the perfect database server has as many processors as possible, as much memory as possible.

If all your databases can be run in memory, this is the best option.

When your...

Also asked and answered here

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=128741

select *

into #TempTable

from (SELECT column_name,column_default

FROM INFORMATION_SCHEMA.COLUMNS

where table_Name ='TMovie' )

and change all other occurancies of "____TEMP____TABLE___" to "#TempTable"

2nd version of fnParseList here

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=76033

DELETE f

FROM (

SELECT ROW_NUMBER() OVER (PARTITION BY Path ORDER BY ID) AS recID

FROM Table1

) AS f

WHERE recID > 1

No, the OS handles this.

See here for a starter about FILESTREAM

http://technet.microsoft.com/en-us/library/bb933993.aspx

The database and OS communicated over the FILESTREAM API.

When you delete a record with FILESTREAM attribute enabled, the operating system...

Once deleted, the FILESTREAM data is under OS control. It can take some time before OS removes the file in the filestream catalogs.

SELECT DATEDIFF(MS, Date1, Date2) / 86400000.0E AS DecimalDay

print cast( ROUND(@real + CAST(0.5E * POWER(0.1E, 2) AS DECIMAL(15, 3)), 2, 1) AS decimal(15, 2))

And that's the culprit. Due to the binary interpretation of REAL and FLOAT datatypes

1 / 2^n + 1 / 2^(n+1) + 1 / 2^(n+2) + 1 / 2^(n+3) + ...

the...

DECLARE@n TINYINT

SET@n = 2

DECLARE@Sample TABLE

(

Value DECIMAL(15, 7)

)

INSERT@Sample

SELECT18.0049 UNION ALL

SELECT18.005

SELECTValue,

ROUND(Value + CAST(0.5E * POWER(0.1E, @n) AS DECIMAL(15, 7)), @n, 1)

FROM@Sample

Add BatchSize option for your BULK INSERT operation.

Set to approx 1000 records.

You can use replication.

And without the CASE thingy

SELECTZIP + COALESCE('-' + PlusFour, '') AS FullZIP

FROM[Address]

There's nothing more to say that I wanted to experiment with a SQL Server instance too see how...

Just a note, SSCommitted is a status, not an Alias. 😉