Showing posts with label documentation. Show all posts
Showing posts with label documentation. Show all posts

Thursday, February 16, 2012

Capacity Planning for OLTP Database Server

Is there any decent documentation for estimating storage, memory, and CPU reqirements for new SQL Server databases?IMHO... nothing that is too great.
However, Compaq and Dell both have SQL sizing tools on thier www site that
you might want to review...
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Charlie Duffy" <charles.t.duffy@.verizon.com> wrote in message
news:90A54F85-2D52-457A-9E8A-95A3AD5B509A@.microsoft.com...
> Is there any decent documentation for estimating storage, memory, and CPU
reqirements for new SQL Server databases?
>

Tuesday, February 14, 2012

Cant use the NTEXT datatype in SQLCLR scalar-valued functions

From the SQL Server documentation :

"The input parameters and the type returned from a SVF can be any of the scalar data types supported by SQL Server, exceptrowversion,text,ntext,image,timestamp,table, orcursor"

This is a problem for me. Here's what I'm trying to do :

I have an NTEXT field in one of my tables. I want to run regular expressions on this field, and return the results from a stored procedure. Since SQL Server doesn't provide facilities to perform regular expressions, I need to use an SQLCLR function. I would have no problem doing this if my field was nvarchar. However, this field needs to be variable in length - I cannot set an upper bound. This is why I'm using NTEXT and not nvarchar in the first place.

Is there a solution to this problem? I can't imagine that I'm the only person who wants to pass strings of arbitrary size to an SQLCLR function.

The sql server 2005 nvarchar(max) is the same as sql server 2000 nText

http://msdn2.microsoft.com/en-us/library/ms178158.aspx

|||Cool. Thanks for the tip. I'll give this a shot and report back.