Viewing 15 posts - 1,096 through 1,110 (of 2,636 total)
I suggest that you search for "long running jobs" on this site. There are several good articles with examples that I used when I was developing a job to...
April 23, 2008 at 10:48 am
Yes, you can use the wizard to import/export to/from a SQL 2000 database. It seems to work better if you use the OLE DB data source provider.
April 23, 2008 at 10:33 am
It will work if you install the DTS 2000 runtime on the 64-bit server. It's part of the "Microsoft SQL Server 2005 Backward Compatibility Components" download at http://www.microsoft.com/downloads/details.aspx?FamilyID=df0ba5aa-b4bd-4705-aa0a-b477ba72a9cb&DisplayLang=en. ...
April 22, 2008 at 4:59 pm
Will,
You don't mention which edition of SQL 2005 you're interested in, but there is a big priced difference between Standard Edition and Enterprise Edition. A $25,000 quote sounds like...
April 22, 2008 at 9:36 am
I don't understand your comment Matt. The variables in my example are different than the ones in the OP's WHERE clause.
April 21, 2008 at 10:09 am
You're not setting the columns to any values. You should have somthing like:
SET [Application_Vendor] = @vendorval
,[Application_Name] = @nameval
...
April 18, 2008 at 11:28 am
When you created the login, did you specify the MUST_CHANGE option of CREATE LOGIN or, if you used Management Studio, did you leave the box checked that says, "User must...
April 17, 2008 at 5:01 pm
I like to use Tempdb as the default database. It's always there and there's nothing for a user to mess up.
April 17, 2008 at 4:55 pm
It most likely fails when run in a job step because the package is run by the login that runs SQL Server Agent, which is not the login that created...
April 17, 2008 at 4:48 pm
You won't get that error again since you're restoring a 2005 backup on a 2005 instance.
April 17, 2008 at 2:23 pm
It's not the edition that's causing the problem. Version 8.00 is SQL Server 2000 and version 9.00 is SQL server 2005. I assume that the backup was made...
April 16, 2008 at 5:57 pm
Can you clarify your problem? Do you have a functioning database but no backups? What is the recovery model of the database?
April 16, 2008 at 5:37 pm
Run this in a query window on both servers:
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
April 16, 2008 at 5:29 pm
It could be that the task that executes the stored procedure is being blocked by another task in the package. Are you using workflow to control execution of successive...
April 16, 2008 at 5:23 pm
Viewing 15 posts - 1,096 through 1,110 (of 2,636 total)