http://www.cpuid.com/cpuz.php

Not only does it provide the above data but also

Technology 90 nm

Core Speed 2666.7 MHz

Multiplier x Bus speed 16.0 x 166.7 MHz

Rated Bus speed 666.7 MHz...

There's a nice little utility called CPU-z. It will provide you a nice little report of your processor (make, code name, cores, and even if Hyper Threading is turned on)...

---

That's why I prefaced mine with the ever popular disclaimer "It depends" 🙂

Gail, while I tend to agree I've run into some very bad choices at client sites. One company had a non clustered inde on their status column (foreign key to...

Sandy, in typical SQL Server speak the answer is "It depends". Look at the data in that column. Does it have a wide range of distinct values or a few...

IT depends on the number and type of counters used but in my eperience I've never seen more thant a 1% or 2% increase in CPU.

How about this...

put the queries you want executed in the after house window inside a procedure or procdures. Create a user with explicit permissions to execute them. Deny execute to...

If you want to know how SQL Server is changing the port when you use EM, Configuration Manager, etc... Start a Profiler trace then make the change.

You can also use SQL 2005's PIVOT function.

Doug

ok, 3rd time's a charm...

update table

set {column name} =

replace( replace( {column name}, '!', ''), '''','')

where

charindex( '!', {column name}...

Darn code block! It removed the "column name" parameter

update table

set {column name}, '!', ''), '''','')

where

charindex( '!', {column name} ) > ...

If I understand correctly you're just replacing the double quote ('') and ! correct? The replace function can be nested like this...

update table

set ...

Can you provide sample code?

DAB

Are usernmae/password part of the query string?

Then use '?username=' + @username + '&' + 'password=' + @password

Remember, xp_cmdshell is a synchronous process and control will not return to SQL Server until this process is complete. Therefore, when executing a process outside of the SQL Server environment...