Viewing 15 posts - 1 through 15 (of 23 total)
Nope, I wish it was that easy, there are some rows in that table that have more than 8000 chars in them, that is why varchar(8000) was not used in...
August 3, 2007 at 11:19 am
FYI, I have made some chenges to this that I belive will also help:
August 2, 2007 at 1:14 pm
SELECT max(DATALENGTH(content_blob))
FROM content_blob
WHERE (BLOB_TYPE_ID IN(3,9)
and CONTENT_BLOB LIKE '%''''%')
RETURNS 5006
August 2, 2007 at 12:15 pm
The correct answer to this question all depends on what version of SQL Server you are using. SCHEMA_NAME() is only a recognized function in SQL Server 2005, not in SQL...
March 22, 2006 at 11:26 am
The most important point you made in your entire article during an interview is to RELAX. NEVER appear DESPERATE or NERVOUS in a interview. That will end it faster than...
February 23, 2006 at 8:24 am
Clever, but I don't recommend doing this at all. You are really risking getting things really screwed up! You are better off just scripting out replication including the jobs, removing...
February 1, 2006 at 8:08 am
I have been a Senior DBA for many years and the one thing I have learned the hard way is "CYA" at all times...I have seen too many talented and hard-working...
December 30, 2005 at 9:29 am
I also agree. Password protection and encryption are two different things related to security. Simply putting a password on a backup does not equate to ispo facto encryption.
September 1, 2005 at 9:03 am
You forgot about the fifth choice:
5. Fire the junior DBA for dropping a production database without communicating this beforehand to anyone. If it was simply an accident then take away...
June 30, 2005 at 8:04 am
Remi,
Not true, NOT EXISTS is always better on performance than NOT IN. This is an excerpt right from SQL Server Performance Tuning Tips (http://www.sql-server-performance.com/):
If you currently...
June 23, 2005 at 2:02 pm
I agree, I think the 2 choices to this question should have been:
1. NOT EXISTS
2. NOT IN
Then, this question would have been more relevant.
June 23, 2005 at 7:56 am
Good article, and number of valuable lessons come out of this:
1. Never do an update directly to a production db without first testing this in development or QA environment first...
June 16, 2005 at 2:23 pm
Absolutely 100% wholeheartedly agree with you and your excellent and very overlooked point about Sarbanes-Oxley makes the whole discussion about the demise of production DBA's a moot point. Great article!!!!!
Travis
June 2, 2005 at 10:05 am
This article is redundant in my opinion since there is already a KB article that has been out for quite some time that covers this topic very well.
November 30, 2004 at 11:15 am
If the question is what is wrong? Yet another BS question designed to trick people. When are the people in charge at SQLServerCentral.com going to put a stop to...
November 17, 2004 at 8:32 am
Viewing 15 posts - 1 through 15 (of 23 total)