Forum Replies Created

Viewing 15 posts - 1,651 through 1,665 (of 2,636 total)

  • RE: SSIS shedule job error

    Aside from the GUID thing I mentioned, I didn't have any trouble running a legacy DTS package in a job in SQL 2005.  I guess you should make sure the...

  • RE: Problem in Restoring Database with different Name

    I assume databases 'A' and 'B' are in the same instance.  Can you post the RESTORE command you used?  You should use WITH MOVE to create new database files for...

  • RE: Saving Linked servers and other things

    Ed,

    There's a script in the script section of this site that will script out all the linked servers in an instance.  I used it recently to transfer linked servers from...

  • RE: SSIS shedule job error

    Stacey,

    Are you storing the package as a legacy DTS package and running it using DTSRun?  If so, are you using the GUID to identify the package?  I found that packages...

  • RE: Move stored procedures to different server

    Yeah, I like it a lot.  It even came in handy when I was transferring packages from a SQL2000 instance to a new SQL2005 instance and had to save them...

  • RE: DTS jobs forced to run consecutively?

    Tony,

    Only one instance of a job can be run at a time, so if it's still  running when the next run is scheduled, SQL Server Agent will not start it. ...

  • RE: Automatic Backup/restore

    Hi Hassan,

    Could you explain a little about what you want to do with the second instance?  It kind of sounds like you're describing log shipping when you talk about automatic...

  • RE: How to move jobs ?

    As stated above, there's no comprehensive way to move all those objects.  You'll have to move the tables, stored procedures, packages, and jobs separately. 

    Tables and stored procedures can either...

  • RE: Move stored procedures to different server

    The easiest way to do that is to open the package in DTS Designer then 'Save As' and name the server you want to transfer it to.  DTSBackup 2000 available...

  • RE: How to find SSIS Package depends?

    Unfortunately, no such tools exist in SQL Server.  The only way to see package properties is to open it or script it out to a file that can be edited.

    Greg

  • RE: Move stored procedures to different server

    You can use the Copy SQL Server Objects task in DTS to transfer stored procedures directly.  It gives you the option of selecting which stored procedures you want to move. ...

  • RE: SQL server 2005 as SQL Server 2000

    You've got to test.  We've begun the upgrade/migration process by creating a SQL 2005 test instance and migrating some databases, logins, jobs, and DTS packages.  Now we're testing our applications. 

    Microsoft...

  • RE: some common DBA questions, since i am new here

    See this article for tried and true methods of transferring logins: http://support.microsoft.com/kb/246133/en-us  I've used the sp_help_revlogin described many times.

    There's a Rebuild Master utility in SQL 2000.  Rebuilding master removes...

  • RE: Editing DTS source soce

    There's a script in the script secton of this site that copies all packages stored in msdb to text files.  I've used it for packages that don't have passwords and...

  • RE: copy tables from 1 db to other db

    Even quicker, use SELECT INTO:

    SELECT sourcetable.*

    INTO targetdb..targettable

    FROM sourcetable

    To answer the original question, yes, DTS can copy any or all tables from one database to another.  Just use the import/export wizard.

    Greg

     

Viewing 15 posts - 1,651 through 1,665 (of 2,636 total)