Database name not found in the Edit job step in SQL Server Enterprise Manager

Hi,

I need help. I transferred my database from one server to another by
using attach detach process.I created all the jobs which existed in the

old server in the new server. Everything looked fine but a couple of
jobs is a giving me some problems. When I try to edit the job step I
could see that the database dropdown list doesn't contain the database
name(which I transferred from the old server)

Does anyone have any idea about it.

Thanks
Arun(arunkumar_m2001@.yahoo.com) writes:
> I need help. I transferred my database from one server to another by
> using attach detach process.I created all the jobs which existed in the
> old server in the new server. Everything looked fine but a couple of
> jobs is a giving me some problems. When I try to edit the job step I
> could see that the database dropdown list doesn't contain the database
> name(which I transferred from the old server)
>
> Does anyone have any idea about it.

Have you tried simply closing down Enterprise Manager and starting it
again? I did a quick test, and it appears that the job-step dialogue
caches the database list, so it may not have seen the new database yet.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Database Modelling in UML

The Methods & Tools newsletter has released in its archive section the
article "Database Modelling in UML". This article offers a step by step
approach to transform a UML object-oriented class model in a purely
relational database.

http://www.methodsandtools.com/archive/archive.php?id=9Franco Martinig via SQLMonster.com wrote:

> The Methods & Tools newsletter has released in its archive section the
> article "Database Modelling in UML". This article offers a step by step
> approach to transform a UML object-oriented class model in a purely
> relational database.
> http://www.methodsandtools.com/archive/archive.php?id=9

The article is rather difficult to believe after lines like this:

"The relational model only offers a public data access model. All data is
equally exposed and open to any process to update, query or manipulate it.
Information hiding is unknown."

This statement is true in the same sense that it is true that you have to
turn a crank on the front of a car to get it started. It depends on
whether or not you are Rip Van Winkle.

I kept reading looking for a qualifier, but the mistake is repeated later
on, "The relational model exposes all data equally, with limited support
for associating behaviour with data elements through triggers, indexes and
constraints."

--
Kenneth Downs
Secure Data Software, Inc.
(Ken)nneth@.(Sec)ure(Dat)a(.com)|||Perhaps for another perspective, read:
http://www.dbdebunk.com/page/page/622916.htm
http://www.dbdebunk.com/page/page/622867.htm

--
Anith

Database Mirroring

Hi All
Can anyone point me in the right direction to any references or step by step
instructions for installing database mirroring?
ThanksBooks On-Line is the best starting point. I would download the latest
version first.
http://www.microsoft.com/technet/pr...oads/books.mspx
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David" <David@.discussions.microsoft.com> wrote in message
news:F2F5AAA2-785B-45DA-A1D6-C5BFB3A69C67@.microsoft.com...
> Hi All
> Can anyone point me in the right direction to any references or step by
> step
> instructions for installing database mirroring?
> Thanks
>|||Take a look at this paper by Ron Talmage
http://www.microsoft.com/technet/pr...5/dbmirror.mspx
Ben Nevarez, MCDBA, OCP
Database Administrator
"David" wrote:

> Hi All
> Can anyone point me in the right direction to any references or step by st
ep
> instructions for installing database mirroring?
> Thanks
>

Database Mirroring

Hi All
Can anyone point me in the right direction to any references or step by step
instructions for installing database mirroring?
ThanksBooks On-Line is the best starting point. I would download the latest
version first.
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David" <David@.discussions.microsoft.com> wrote in message
news:F2F5AAA2-785B-45DA-A1D6-C5BFB3A69C67@.microsoft.com...
> Hi All
> Can anyone point me in the right direction to any references or step by
> step
> instructions for installing database mirroring?
> Thanks
>|||Take a look at this paper by Ron Talmage
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
Ben Nevarez, MCDBA, OCP
Database Administrator
"David" wrote:
> Hi All
> Can anyone point me in the right direction to any references or step by step
> instructions for installing database mirroring?
> Thanks
>

Database migration from Sybase database to SQL Server 2005

We are going to be migrating an application and the first step is to
migration the Sybase database to SQL Server 2005 database. Can anyone shed
some light into this and help me understand the process involved? What are
the possible pitfalls? What should the approach be?
Thanks,
Newbie
Hi
I have never migrated from Sybase, but I would expect to treat it in a
similar way to migrating from SQL 6.5 to a higher version. If your code is
not already in Source Code control, then I you may want to make that a
pre-requisite for the migration. You should then be able to get to a stage
where you can build a SQL 2005 database from this code rather than use a
migration tool. When migrating the data you can use SSIS, although if you
require more control it may be worth considering using a two stage process
such as exporting the data into flat files and then importing it.
John
"NewToMigration" wrote:

> We are going to be migrating an application and the first step is to
> migration the Sybase database to SQL Server 2005 database. Can anyone shed
> some light into this and help me understand the process involved? What are
> the possible pitfalls? What should the approach be?
> Thanks,
> Newbie
>
|||Thanks, John, for your response. I will make sure I keep this in mind.
Regards,
Newbie
John Bell wrote:[vbcol=seagreen]
>Hi
>I have never migrated from Sybase, but I would expect to treat it in a
>similar way to migrating from SQL 6.5 to a higher version. If your code is
>not already in Source Code control, then I you may want to make that a
>pre-requisite for the migration. You should then be able to get to a stage
>where you can build a SQL 2005 database from this code rather than use a
>migration tool. When migrating the data you can use SSIS, although if you
>require more control it may be worth considering using a two stage process
>such as exporting the data into flat files and then importing it.
>John
>[quoted text clipped - 3 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200602/1
|||Hi
I forgot to add...
You will need to make sure that you do a full regression test.
Therefore having the "old" system to compare against will be useful!
John
"NewToMigration via droptable.com" wrote:

> Thanks, John, for your response. I will make sure I keep this in mind.
> Regards,
> Newbie
> John Bell wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200602/1
>

Database migration from Sybase database to SQL Server 2005

We are going to be migrating an application and the first step is to
migration the Sybase database to SQL Server 2005 database. Can anyone shed
some light into this and help me understand the process involved? What are
the possible pitfalls? What should the approach be?
Thanks,
NewbieHi
I have never migrated from Sybase, but I would expect to treat it in a
similar way to migrating from SQL 6.5 to a higher version. If your code is
not already in Source Code control, then I you may want to make that a
pre-requisite for the migration. You should then be able to get to a stage
where you can build a SQL 2005 database from this code rather than use a
migration tool. When migrating the data you can use SSIS, although if you
require more control it may be worth considering using a two stage process
such as exporting the data into flat files and then importing it.
John
"NewToMigration" wrote:

> We are going to be migrating an application and the first step is to
> migration the Sybase database to SQL Server 2005 database. Can anyone shed
> some light into this and help me understand the process involved? What are
> the possible pitfalls? What should the approach be?
> Thanks,
> Newbie
>|||Thanks, John, for your response. I will make sure I keep this in mind.
Regards,
Newbie
John Bell wrote:[vbcol=seagreen]
>Hi
>I have never migrated from Sybase, but I would expect to treat it in a
>similar way to migrating from SQL 6.5 to a higher version. If your code is
>not already in Source Code control, then I you may want to make that a
>pre-requisite for the migration. You should then be able to get to a stage
>where you can build a SQL 2005 database from this code rather than use a
>migration tool. When migrating the data you can use SSIS, although if you
>require more control it may be worth considering using a two stage process
>such as exporting the data into flat files and then importing it.
>John
>
>[quoted text clipped - 3 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200602/1|||Hi
I forgot to add...
You will need to make sure that you do a full regression test.
Therefore having the "old" system to compare against will be useful!
John
"NewToMigration via droptable.com" wrote:

> Thanks, John, for your response. I will make sure I keep this in mind.
> Regards,
> Newbie
> John Bell wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200602/1
>

Database migration from Sybase database to SQL Server 2005

We are going to be migrating an application and the first step is to
migration the Sybase database to SQL Server 2005 database. Can anyone shed
some light into this and help me understand the process involved? What are
the possible pitfalls? What should the approach be?
Thanks,
NewbieHi
I have never migrated from Sybase, but I would expect to treat it in a
similar way to migrating from SQL 6.5 to a higher version. If your code is
not already in Source Code control, then I you may want to make that a
pre-requisite for the migration. You should then be able to get to a stage
where you can build a SQL 2005 database from this code rather than use a
migration tool. When migrating the data you can use SSIS, although if you
require more control it may be worth considering using a two stage process
such as exporting the data into flat files and then importing it.
John
"NewToMigration" wrote:
> We are going to be migrating an application and the first step is to
> migration the Sybase database to SQL Server 2005 database. Can anyone shed
> some light into this and help me understand the process involved? What are
> the possible pitfalls? What should the approach be?
> Thanks,
> Newbie
>|||Thanks, John, for your response. I will make sure I keep this in mind.
Regards,
Newbie
John Bell wrote:
>Hi
>I have never migrated from Sybase, but I would expect to treat it in a
>similar way to migrating from SQL 6.5 to a higher version. If your code is
>not already in Source Code control, then I you may want to make that a
>pre-requisite for the migration. You should then be able to get to a stage
>where you can build a SQL 2005 database from this code rather than use a
>migration tool. When migrating the data you can use SSIS, although if you
>require more control it may be worth considering using a two stage process
>such as exporting the data into flat files and then importing it.
>John
>> We are going to be migrating an application and the first step is to
>> migration the Sybase database to SQL Server 2005 database. Can anyone shed
>[quoted text clipped - 3 lines]
>> Thanks,
>> Newbie
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200602/1|||Hi
I forgot to add...
You will need to make sure that you do a full regression test.
Therefore having the "old" system to compare against will be useful!
John
"NewToMigration via SQLMonster.com" wrote:
> Thanks, John, for your response. I will make sure I keep this in mind.
> Regards,
> Newbie
> John Bell wrote:
> >Hi
> >
> >I have never migrated from Sybase, but I would expect to treat it in a
> >similar way to migrating from SQL 6.5 to a higher version. If your code is
> >not already in Source Code control, then I you may want to make that a
> >pre-requisite for the migration. You should then be able to get to a stage
> >where you can build a SQL 2005 database from this code rather than use a
> >migration tool. When migrating the data you can use SSIS, although if you
> >require more control it may be worth considering using a two stage process
> >such as exporting the data into flat files and then importing it.
> >
> >John
> >
> >> We are going to be migrating an application and the first step is to
> >> migration the Sybase database to SQL Server 2005 database. Can anyone shed
> >[quoted text clipped - 3 lines]
> >> Thanks,
> >> Newbie
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200602/1
>sql