do you have dbmail working already on your SQL2000 instance?

sending mail of any kind is going to have that as a prerequisite.

after that, i'd say it's a query in a...

I feel for you, locked into older versions that you have no control over.

Bending this process to your will, you are going to have boatloads of issues: varchar max didn't...

function parameters are not optional the way stored procedures are. All values must be passed, or the default placehodler must be used in it's place

you have to use the default...

here's how i wold do it:

for an instance that i'm resetting or just deploying:

1. in the [source] Reporting Services Configuration Manager, export the encryption key from an instance i want...

as others have implied, this is one of those basic items that a DBA handles.

very often, it's because you've got databases in FULL recovery mode that have had a...

only if you are creating new instances; i think you'll have issues if you import an existing key over an pre-existing SSRS isntallation.

if you have, say five SSRS instances, and...

lloks like you need yet another cumulative update?

https://support.microsoft.com/kb/2008286?wa=wsignin1.0

Error message when you use Database Mail after you apply a SQL Server service pack or cumulative update: "System.IndexOutOfRangeException: timeout"

Print

Email

Article translations

Article ID: 2008286...

sending data to a file is an export.

SQL, natively, does not support file operations; it's always up to an external application, so you use an applciation to connect and save,...

i'm under the impression that the email is supposed to be bracketed, and semi colon delimited when multiple addresses are involved, like this:

"Nescio, Nomen" <nomen.nescio@noreply.com>;"The SQL Administrator" <admin@noreply.com>;

I'm guessing that...

i've had situations where my linked servers odbc drivers get locked up/doinked up in the past, i think related to open transactions in the distributed transaction coordinator,and the only thing...

yes that is correct. you cna change the compatibiolity level at will, and it instantly, dynamically starts affecting the next query that it encounters.

In my experience, there's not much that...

nope it's just a command, but remermber what it does:

all it does is limit queries that use that database to a follow a specific syntax/set of rules....it has nothing to...

i can tell you it's an explicit error that someone coded to capture in your procedure, where someone is using the RAISERROR('some string',11,11).

as noted, read the proc and jump...

i can tell you it's an explicit error that someone coded to capture in your procedure, where someone is using the RAISERROR('some string',16,1).

as noted, read the proc and jump...

i think this is where you need to look into using a full text indexing. that's the way to really handle these kinds of searches.

doing it via LIKE statements requries...