Viewing 15 posts - 2,101 through 2,115 (of 2,636 total)
You can't create or restore a database with DTS. You can only copy objects and data, not the database itself. You should use SQL Server BACKUP and RESTORE for replacing...
March 15, 2006 at 1:06 pm
Truncate permission also defaults to the table owner. If the operator were the owner of the staging tables he or she could truncate them but not others in the database.
Greg
March 9, 2006 at 9:34 am
Maybe, if the job step with the RESTORE command is run as dbo.
March 8, 2006 at 2:15 pm
I haven't done it, but it should be entirely possible providing you have the mysql ODBC driver installed on the SQL Server where you'll execute the DTS package.
Greg
March 8, 2006 at 9:59 am
I recommend "Inside SQL Server 2000" by Kalen Delaney, any of Ken Henderson's books, and SQL Server Books Online, which is SQL Server's user manual and is included with SQL...
March 8, 2006 at 9:53 am
Walter,
My Oracle skills are a little rusty, but why can't you just create a sequence (Oracle's equivalent of SQL Server identity) for the Oracle table and not bother to generate...
March 8, 2006 at 9:44 am
Yvan,
I can recommend Lumigent Log Explorer. We've used it for the past three years and it's worked well.
Greg
March 8, 2006 at 9:28 am
It's possible. SQL Server Agent must run as a domain account and must have permission to write to the remote location. When creating the backup device, enter a UNC path...
March 8, 2006 at 9:26 am
Be aware that a member of dbcreator server role can restore any database in the instance. I believe the only way to restrict the RESTORE permission to a particular database...
March 8, 2006 at 9:12 am
"Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. "
I agree with Luke. Open the package and check the SQL Server connections. My guess is you didn't change the...
March 8, 2006 at 9:02 am
You can add multiple schedules for a job in Enterprise Manager. Open the the job properties, click on the Schedules tab, and click on the New Schedule button. As you...
March 8, 2006 at 8:54 am
I don't think it's a bug. I think the database property ANSI_WARNINGS has been set off for the destination database. See 'SET ANSI_WARNINGS' in BOL.
Greg
March 7, 2006 at 2:58 pm
The message means that the table doesn't exist. Is it owned by someone other than the database owner?
Greg
March 7, 2006 at 2:02 pm
Is MSDM_Import an object in your source database?
Greg
March 6, 2006 at 2:01 pm
You can also use the Import/Export wizard to copy the structure and permissions. Use the third option, "Copy objects and data between SQL Server databases". Check the "Create destination objects"...
March 6, 2006 at 9:07 am
Viewing 15 posts - 2,101 through 2,115 (of 2,636 total)