Perhaps you need to migrate the login information from the old server, or else recreate their logins on the new.

I recommend the O'Reilly book "Transact-SQL Programming" (the one with the hummingbirds) to any newbie. After you have read it, it remains an important and oft used reference.

I have found performance gains by selecting a subset of interest into a temp table and updating off of that. This way, you separate the comparison from the update.

select...

You might try executing the BCP utility within a stored procedure. That way you avoid all the bugs in DTS.

That does the trick! Thank You.

Another method is to create an instance of SQL Server 2000 on your client machine and send mail from your own email software. Create the stored procedures and tables to...

Gee, I guess that's sort of an obvious approach! Thanks!

Here's my solution.

CREATE  PROCEDURE usp_rpt_documents_paging

(

 @USERS_ID INT = NULL

 ,@PIPELINES_ID INT = NULL

 ,@PAGE INT = NULL OUTPUT

 ,@ROWS_PER_PAGE INT = NULL

 ,@DOC_TYPE VARCHAR(255) = NULL

 ,@SORT_CHOICE TINYINT = 0

 ,@SORT_DESC BIT = 0

 ,@TEST TINYINT = 0

)

/***********************************************************************************************************

 Create...

The answer is "no", you cannot use an if statement in a select!

Joe Celko says that all major products have standardized COUNT(*) and COUNT(1) to work with equal efficiency. Does anyone know that not to be the case in SQL Server?

I use the function listed below without any added tables. So I created the given solution above and compared execution plans: they came out the same.

ALTER FUNCTION dbo.udf_strip_non_alphabetic ( @IN_STRING VARCHAR(8000) )

RETURNS...

I recommend never applying complex logic during the data transfer. To import files, load your raw data into a buffer table then process it within a stored procedure. After cleaning and...

I've got it all wrapped up in a function.

CREATE FUNCTION UDF_WEEK_OF( @Date VARCHAR(23) )

RETURNS VARCHAR(23)

AS

BEGIN

 DECLARE @Week_Ending AS VARCHAR(23)

 SELECT @Week_Ending =

    CONVERT(

     VARCHAR

     ,DATEADD( WEEK, DATEPART( WEEK, @Date ) - 1, '1/1/' + CAST(...

If they are using open SQL in their applications rather than stored procedure calls, then they really are bad programmers.

I've wrapped many sprock executions within transactions and never had a problem until the transaction contained the "sp_OA-" extended stored procedures.