There is some information in this forum and on the web:
http://forums.microsoft.com/MSDN/Search/Search.aspx?words=DTS+migration&localechoice=9&SiteID=1&searchscope=forumscope&ForumID=80
http://www.google.com/search?hl=en&q=migration+ssis+to+dts
Showing posts with label old. Show all posts
Showing posts with label old. Show all posts
Friday, March 30, 2012
Migrating from 2000 to 2005
Hello guys, I have vry basic question. I'm migrating from 2000 to 2005. MY question is do we have to recode all packages or just migrating of old 2000 DTS is fine. If so, then I can see only small icon of DTS package in 2005, whihc is not showing the details of DTS. Kindly, explain me what do i really do, migrating old one or re-creating new in 2005. Thanks in Advance
Monday, March 26, 2012
Migrating an app from one cluster to another .. with the same name
Currently migrating a SQL application from an old Win2k cluster to some new
hardware.
The new hardware will run as a Win2K3SP1 cluster.
The App people would like to keep the names the same for all servers and
virtual services so that clients are not affected.
Downtime is not an option.
Whats the easiest way to do this?
Consider a DNS alias.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Rory Niland" <RoryNiland@.discussions.microsoft.com> wrote in message
news:DDCB983B-3F22-4360-8E07-91B02887ABB3@.microsoft.com...
Currently migrating a SQL application from an old Win2k cluster to some new
hardware.
The new hardware will run as a Win2K3SP1 cluster.
The App people would like to keep the names the same for all servers and
virtual services so that clients are not affected.
Downtime is not an option.
Whats the easiest way to do this?
|||Agreed, because you can't rename a SQL machine.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OvlMaCNcFHA.580@.TK2MSFTNGP15.phx.gbl...
> Consider a DNS alias.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "Rory Niland" <RoryNiland@.discussions.microsoft.com> wrote in message
> news:DDCB983B-3F22-4360-8E07-91B02887ABB3@.microsoft.com...
> Currently migrating a SQL application from an old Win2k cluster to some
> new
> hardware.
> The new hardware will run as a Win2K3SP1 cluster.
> The App people would like to keep the names the same for all servers and
> virtual services so that clients are not affected.
> Downtime is not an option.
> Whats the easiest way to do this?
>
hardware.
The new hardware will run as a Win2K3SP1 cluster.
The App people would like to keep the names the same for all servers and
virtual services so that clients are not affected.
Downtime is not an option.
Whats the easiest way to do this?
Consider a DNS alias.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Rory Niland" <RoryNiland@.discussions.microsoft.com> wrote in message
news:DDCB983B-3F22-4360-8E07-91B02887ABB3@.microsoft.com...
Currently migrating a SQL application from an old Win2k cluster to some new
hardware.
The new hardware will run as a Win2K3SP1 cluster.
The App people would like to keep the names the same for all servers and
virtual services so that clients are not affected.
Downtime is not an option.
Whats the easiest way to do this?
|||Agreed, because you can't rename a SQL machine.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OvlMaCNcFHA.580@.TK2MSFTNGP15.phx.gbl...
> Consider a DNS alias.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "Rory Niland" <RoryNiland@.discussions.microsoft.com> wrote in message
> news:DDCB983B-3F22-4360-8E07-91B02887ABB3@.microsoft.com...
> Currently migrating a SQL application from an old Win2k cluster to some
> new
> hardware.
> The new hardware will run as a Win2K3SP1 cluster.
> The App people would like to keep the names the same for all servers and
> virtual services so that clients are not affected.
> Downtime is not an option.
> Whats the easiest way to do this?
>
Friday, March 23, 2012
Migrate VIEW from Access to SQLserver ??
I migrated a DB from Access 2000 to SQLserver 2000.
The tables are OK, but I see the old Access views... as TABLE in
SQLserver!!
Any suggestions?
--Access isn't "smart" enough to upsize its queries into MS SQL Server views
so instead it just runs the query and creates a table from the result.
You'll have to port all of the queries manually (although I'm sure there are
tools or at least guides to help you with this) since Access's SQL differs
from MS SQL Server's SQL. Some of the most common issues I've run in are
that MS SQL Server doesn't have all those handy VB functions and IsNull()
does not work the same way in both.
"YURYSSG" <yuryssg@.yahoo.it> wrote in message
news:2i85qbFjsi78U1@.uni-berlin.de...
> I migrated a DB from Access 2000 to SQLserver 2000.
> The tables are OK, but I see the old Access views... as TABLE in
> SQLserver!!
> Any suggestions?
> --|||"Jonathan Amend" <cephas_is@.hotmail.com> /
: news:40bf8fc4$1_3@.aeinews...
> Access isn't "smart" enough to upsize its queries into MS SQL Server views
> so instead it just runs the query and creates a table from the result.
> You'll have to port all of the queries manually (although I'm sure there
are
> tools or at least guides to help you with this) since Access's SQL differs
> from MS SQL Server's SQL. Some of the most common issues I've run in are
> that MS SQL Server doesn't have all those handy VB functions and IsNull()
> does not work the same way in both.
> "YURYSSG" <yuryssg@.yahoo.it> wrote in message
> news:2i85qbFjsi78U1@.uni-berlin.de...
> > I migrated a DB from Access 2000 to SQLserver 2000.
> > The tables are OK, but I see the old Access views... as TABLE in
> > SQLserver!!
> > Any suggestions?
> > --|||"Jonathan Amend" <cephas_is@.hotmail.com> wrote:
>Access isn't "smart" enough to upsize its queries into MS SQL Server views
>so instead it just runs the query and creates a table from the result.
>You'll have to port all of the queries manually (although I'm sure there are
>tools or at least guides to help you with this) since Access's SQL differs
>from MS SQL Server's SQL. Some of the most common issues I've run in are
>that MS SQL Server doesn't have all those handy VB functions and IsNull()
>does not work the same way in both.
FWIW I was able to programmatically make views out of many of my
Access queries.
I had much more code than this but the basics were as follows.
strNewSQL = adhReplace(Q.SQL, vbCrLf, " ")
strNewSQL = Left(strNewSQL, InStr(strNewSQL, ";") - 1)
strNewSQL = ConvertTrueFalseTo10(strNewSQL)
tagRetryAfterCleanup:
Set myquerydef = dbsPermanent.CreateQueryDef("")
'Q.Name & " DAO Test")
myquerydef.ReturnsRecords = False
myquerydef.Connect = strConnect
myquerydef.SQL = "CREATE VIEW [" & strQueryName & "]
AS " & strNewSQL
myquerydef.Execute
myquerydef.Close
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Migrate SQL Server 2000
Hello. We have a new database server machine that will replace our old
database server machine running SQL 2000 (will take on the same name and ip
address). I was wondering if anyone could recommend or point me to some
info on what is the best method in getting the data from our old soon to be
retired machine to our new machine? Perhaps setting up an empty SQL 2000 on
the new machine and then taking the backup files from the old machine and
doing a restore on each database starting with the master db?...just
wondering if this will affect any of the system databases (master, temp,
msdb, model) like the sql/window logins/passwords and/or other backend
things that should or would need to remain in tact?
Thanks in advance.
Jhttp://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en
This is What you can Read or goto
http://www.microsoft.com/downloads/details.aspx?familyid=1470E86B-7E05-4322-A677-95AB44F12D75&displaylang=en
This is Helpful.
Rest in Short: Just Detach and attach the Databases to the new SQL2K5
Server and change the Compatability Level to 90
As for the DTS PAckages you might have on SQL2000, Well its a whole new
Story. DTS Packages without several connections are easy to migrate,
but Some require to be recreated from Scratch, if you have on of those
smart Developers with you, He will figure out a process in time.
Maninder
MCDBA
On Jan 22, 1:54 pm, "J" <IDontLikeS...@.Nowhere.com> wrote:
> Hello. We have a new database server machine that will replace our old
> database server machine running SQL 2000 (will take on the same name and ip
> address). I was wondering if anyone could recommend or point me to some
> info on what is the best method in getting the data from our old soon to be
> retired machine to our new machine? Perhaps setting up an empty SQL 2000 on
> the new machine and then taking the backup files from the old machine and
> doing a restore on each database starting with the master db?...just
> wondering if this will affect any of the system databases (master, temp,
> msdb, model) like the sql/window logins/passwords and/or other backend
> things that should or would need to remain in tact?
> Thanks in advance.
> J|||Actually both old and new server will be SQL 2000. So I guess I can look at
my first task as a full restore based on all of the backups?
I think we will eventually upgrade to SQL 2005 so I'll definitely keep your
helpful info in mind. Thanks for the info Maninder. I totally appreciate
it.
J
"Maninder" <msdhanjal@.gmail.com> wrote in message
news:1169493039.530765.30020@.s34g2000cwa.googlegroups.com...
> http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en
> This is What you can Read or goto
> http://www.microsoft.com/downloads/details.aspx?familyid=1470E86B-7E05-4322-A677-95AB44F12D75&displaylang=en
> This is Helpful.
> Rest in Short: Just Detach and attach the Databases to the new SQL2K5
> Server and change the Compatability Level to 90
> As for the DTS PAckages you might have on SQL2000, Well its a whole new
> Story. DTS Packages without several connections are easy to migrate,
> but Some require to be recreated from Scratch, if you have on of those
> smart Developers with you, He will figure out a process in time.
> Maninder
> MCDBA
>
> On Jan 22, 1:54 pm, "J" <IDontLikeS...@.Nowhere.com> wrote:
>> Hello. We have a new database server machine that will replace our old
>> database server machine running SQL 2000 (will take on the same name and
>> ip
>> address). I was wondering if anyone could recommend or point me to some
>> info on what is the best method in getting the data from our old soon to
>> be
>> retired machine to our new machine? Perhaps setting up an empty SQL 2000
>> on
>> the new machine and then taking the backup files from the old machine and
>> doing a restore on each database starting with the master db?...just
>> wondering if this will affect any of the system databases (master, temp,
>> msdb, model) like the sql/window logins/passwords and/or other backend
>> things that should or would need to remain in tact?
>> Thanks in advance.
>> J
>|||Thanks for the insightful info Lucas. Mucha appreciated.
Take care,
J
"Lucas Kartawidjaja" <LucasKartawidjaja@.discussions.microsoft.com> wrote in
message news:A92C9C5E-10EE-4182-8ED3-2B44450BC793@.microsoft.com...
> You could either:
> -. Do a back up the database on your old database and restore of your
> database on your new server.
> -. Do an dettach and attach of your database data and log file.
> Personally, I usually choose the backup and restore approach, just as you
> said. Also you might need to restore the system databases: master, and
> msdb
> (at the very least), if you want to bring over the login information, and
> also the job information. If you want you can also backup and restore the
> model database.
> http://msdn2.microsoft.com/en-us/library/ms190190.aspx
> Lucas
> For info on backup and restore system database:
>
> "J" wrote:
>> Actually both old and new server will be SQL 2000. So I guess I can look
>> at
>> my first task as a full restore based on all of the backups?
>> I think we will eventually upgrade to SQL 2005 so I'll definitely keep
>> your
>> helpful info in mind. Thanks for the info Maninder. I totally
>> appreciate
>> it.
>> J
>> "Maninder" <msdhanjal@.gmail.com> wrote in message
>> news:1169493039.530765.30020@.s34g2000cwa.googlegroups.com...
>> > http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en
>> > This is What you can Read or goto
>> > http://www.microsoft.com/downloads/details.aspx?familyid=1470E86B-7E05-4322-A677-95AB44F12D75&displaylang=en
>> >
>> > This is Helpful.
>> >
>> > Rest in Short: Just Detach and attach the Databases to the new SQL2K5
>> > Server and change the Compatability Level to 90
>> >
>> > As for the DTS PAckages you might have on SQL2000, Well its a whole new
>> > Story. DTS Packages without several connections are easy to migrate,
>> > but Some require to be recreated from Scratch, if you have on of those
>> > smart Developers with you, He will figure out a process in time.
>> >
>> > Maninder
>> > MCDBA
>> >
>> >
>> > On Jan 22, 1:54 pm, "J" <IDontLikeS...@.Nowhere.com> wrote:
>> >> Hello. We have a new database server machine that will replace our
>> >> old
>> >> database server machine running SQL 2000 (will take on the same name
>> >> and
>> >> ip
>> >> address). I was wondering if anyone could recommend or point me to
>> >> some
>> >> info on what is the best method in getting the data from our old soon
>> >> to
>> >> be
>> >> retired machine to our new machine? Perhaps setting up an empty SQL
>> >> 2000
>> >> on
>> >> the new machine and then taking the backup files from the old machine
>> >> and
>> >> doing a restore on each database starting with the master db?...just
>> >> wondering if this will affect any of the system databases (master,
>> >> temp,
>> >> msdb, model) like the sql/window logins/passwords and/or other backend
>> >> things that should or would need to remain in tact?
>> >>
>> >> Thanks in advance.
>> >>
>> >> J
>> >
>>
database server machine running SQL 2000 (will take on the same name and ip
address). I was wondering if anyone could recommend or point me to some
info on what is the best method in getting the data from our old soon to be
retired machine to our new machine? Perhaps setting up an empty SQL 2000 on
the new machine and then taking the backup files from the old machine and
doing a restore on each database starting with the master db?...just
wondering if this will affect any of the system databases (master, temp,
msdb, model) like the sql/window logins/passwords and/or other backend
things that should or would need to remain in tact?
Thanks in advance.
Jhttp://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en
This is What you can Read or goto
http://www.microsoft.com/downloads/details.aspx?familyid=1470E86B-7E05-4322-A677-95AB44F12D75&displaylang=en
This is Helpful.
Rest in Short: Just Detach and attach the Databases to the new SQL2K5
Server and change the Compatability Level to 90
As for the DTS PAckages you might have on SQL2000, Well its a whole new
Story. DTS Packages without several connections are easy to migrate,
but Some require to be recreated from Scratch, if you have on of those
smart Developers with you, He will figure out a process in time.
Maninder
MCDBA
On Jan 22, 1:54 pm, "J" <IDontLikeS...@.Nowhere.com> wrote:
> Hello. We have a new database server machine that will replace our old
> database server machine running SQL 2000 (will take on the same name and ip
> address). I was wondering if anyone could recommend or point me to some
> info on what is the best method in getting the data from our old soon to be
> retired machine to our new machine? Perhaps setting up an empty SQL 2000 on
> the new machine and then taking the backup files from the old machine and
> doing a restore on each database starting with the master db?...just
> wondering if this will affect any of the system databases (master, temp,
> msdb, model) like the sql/window logins/passwords and/or other backend
> things that should or would need to remain in tact?
> Thanks in advance.
> J|||Actually both old and new server will be SQL 2000. So I guess I can look at
my first task as a full restore based on all of the backups?
I think we will eventually upgrade to SQL 2005 so I'll definitely keep your
helpful info in mind. Thanks for the info Maninder. I totally appreciate
it.
J
"Maninder" <msdhanjal@.gmail.com> wrote in message
news:1169493039.530765.30020@.s34g2000cwa.googlegroups.com...
> http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en
> This is What you can Read or goto
> http://www.microsoft.com/downloads/details.aspx?familyid=1470E86B-7E05-4322-A677-95AB44F12D75&displaylang=en
> This is Helpful.
> Rest in Short: Just Detach and attach the Databases to the new SQL2K5
> Server and change the Compatability Level to 90
> As for the DTS PAckages you might have on SQL2000, Well its a whole new
> Story. DTS Packages without several connections are easy to migrate,
> but Some require to be recreated from Scratch, if you have on of those
> smart Developers with you, He will figure out a process in time.
> Maninder
> MCDBA
>
> On Jan 22, 1:54 pm, "J" <IDontLikeS...@.Nowhere.com> wrote:
>> Hello. We have a new database server machine that will replace our old
>> database server machine running SQL 2000 (will take on the same name and
>> ip
>> address). I was wondering if anyone could recommend or point me to some
>> info on what is the best method in getting the data from our old soon to
>> be
>> retired machine to our new machine? Perhaps setting up an empty SQL 2000
>> on
>> the new machine and then taking the backup files from the old machine and
>> doing a restore on each database starting with the master db?...just
>> wondering if this will affect any of the system databases (master, temp,
>> msdb, model) like the sql/window logins/passwords and/or other backend
>> things that should or would need to remain in tact?
>> Thanks in advance.
>> J
>|||Thanks for the insightful info Lucas. Mucha appreciated.
Take care,
J
"Lucas Kartawidjaja" <LucasKartawidjaja@.discussions.microsoft.com> wrote in
message news:A92C9C5E-10EE-4182-8ED3-2B44450BC793@.microsoft.com...
> You could either:
> -. Do a back up the database on your old database and restore of your
> database on your new server.
> -. Do an dettach and attach of your database data and log file.
> Personally, I usually choose the backup and restore approach, just as you
> said. Also you might need to restore the system databases: master, and
> msdb
> (at the very least), if you want to bring over the login information, and
> also the job information. If you want you can also backup and restore the
> model database.
> http://msdn2.microsoft.com/en-us/library/ms190190.aspx
> Lucas
> For info on backup and restore system database:
>
> "J" wrote:
>> Actually both old and new server will be SQL 2000. So I guess I can look
>> at
>> my first task as a full restore based on all of the backups?
>> I think we will eventually upgrade to SQL 2005 so I'll definitely keep
>> your
>> helpful info in mind. Thanks for the info Maninder. I totally
>> appreciate
>> it.
>> J
>> "Maninder" <msdhanjal@.gmail.com> wrote in message
>> news:1169493039.530765.30020@.s34g2000cwa.googlegroups.com...
>> > http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en
>> > This is What you can Read or goto
>> > http://www.microsoft.com/downloads/details.aspx?familyid=1470E86B-7E05-4322-A677-95AB44F12D75&displaylang=en
>> >
>> > This is Helpful.
>> >
>> > Rest in Short: Just Detach and attach the Databases to the new SQL2K5
>> > Server and change the Compatability Level to 90
>> >
>> > As for the DTS PAckages you might have on SQL2000, Well its a whole new
>> > Story. DTS Packages without several connections are easy to migrate,
>> > but Some require to be recreated from Scratch, if you have on of those
>> > smart Developers with you, He will figure out a process in time.
>> >
>> > Maninder
>> > MCDBA
>> >
>> >
>> > On Jan 22, 1:54 pm, "J" <IDontLikeS...@.Nowhere.com> wrote:
>> >> Hello. We have a new database server machine that will replace our
>> >> old
>> >> database server machine running SQL 2000 (will take on the same name
>> >> and
>> >> ip
>> >> address). I was wondering if anyone could recommend or point me to
>> >> some
>> >> info on what is the best method in getting the data from our old soon
>> >> to
>> >> be
>> >> retired machine to our new machine? Perhaps setting up an empty SQL
>> >> 2000
>> >> on
>> >> the new machine and then taking the backup files from the old machine
>> >> and
>> >> doing a restore on each database starting with the master db?...just
>> >> wondering if this will affect any of the system databases (master,
>> >> temp,
>> >> msdb, model) like the sql/window logins/passwords and/or other backend
>> >> things that should or would need to remain in tact?
>> >>
>> >> Thanks in advance.
>> >>
>> >> J
>> >
>>
Monday, March 19, 2012
Migrate from old SQL ce Version in to new SQL Server/mobile
Hi all,
I'm in a middle of a server migration,
Old server:
SBS 2003 sp1 with SQL server 2000 and SQL server CE
New server:
SBS R2 with SQL server 2005 and SQL server mobile
I have tried to find on internet how to migrate all my databases that i have on old server in to the new one, but i can't find anything on it.
In old server i have replications set and my CE database is on SQL 2000 how this will fit on SQL 2005 / SQL mobile?
If some one can point me on good way i appreciate.
Cheers,
For upgrading from SQL CE 2.0 to SQL Compact 3.1, this MSDN article might be useful:
http://msdn2.microsoft.com/en-us/library/bb286906.aspx
(Upgrading from SQL Server CE 2.0 to SQL Server 2005 Compact Edition)
|||Hi tks, for the replay,
But my problem is not on pocket pc side but server side.
On my old sever i use SQL CE so my pockets can get data from SQL server, now on this new SQL server version; we have this new option "SQL Mobile".
How cold i backup databases from old SQL server 2000 and how to restore on the new SQL server 2005.
If possible to backup and restore, were do i have to restore in Mobile or in SQL server 2005.
Regards,
|||This 350 page document should keep you happy for a while (including "Upgrading replicated databases"):
http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en
Migrate from old SQL ce Version in to new SQL Server/mobile
Hi all,
I'm in a middle of a server migration,
Old server:
SBS 2003 sp1 with SQL server 2000 and SQL server CE
New server:
SBS R2 with SQL server 2005 and SQL server mobile
I have tried to find on internet how to migrate all my databases that i have on old server in to the new one, but i can't find anything on it.
In old server i have replications set and my CE database is on SQL 2000 how this will fit on SQL 2005 / SQL mobile?
If some one can point me on good way i appreciate.
Cheers,
For upgrading from SQL CE 2.0 to SQL Compact 3.1, this MSDN article might be useful:
http://msdn2.microsoft.com/en-us/library/bb286906.aspx
(Upgrading from SQL Server CE 2.0 to SQL Server 2005 Compact Edition)
|||Hi tks, for the replay,
But my problem is not on pocket pc side but server side.
On my old sever i use SQL CE so my pockets can get data from SQL server, now on this new SQL server version; we have this new option "SQL Mobile".
How cold i backup databases from old SQL server 2000 and how to restore on the new SQL server 2005.
If possible to backup and restore, were do i have to restore in Mobile or in SQL server 2005.
Regards,
|||This 350 page document should keep you happy for a while (including "Upgrading replicated databases"):
http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en
Migrate from old SQL ce Version in to new SQL Server/mobile
Hi all,
I'm in a middle of a server migration,
Old server:
SBS 2003 sp1 with SQL server 2000 and SQL server CE
New server:
SBS R2 with SQL server 2005 and SQL server mobile
I have tried to find on internet how to migrate all my databases that i have on old server in to the new one, but i can't find anything on it.
In old server i have replications set and my CE database is on SQL 2000 how this will fit on SQL 2005 / SQL mobile?
If some one can point me on good way i appreciate.
Cheers,
For upgrading from SQL CE 2.0 to SQL Compact 3.1, this MSDN article might be useful:
http://msdn2.microsoft.com/en-us/library/bb286906.aspx
(Upgrading from SQL Server CE 2.0 to SQL Server 2005 Compact Edition)
|||Hi tks, for the replay,
But my problem is not on pocket pc side but server side.
On my old sever i use SQL CE so my pockets can get data from SQL server, now on this new SQL server version; we have this new option "SQL Mobile".
How cold i backup databases from old SQL server 2000 and how to restore on the new SQL server 2005.
If possible to backup and restore, were do i have to restore in Mobile or in SQL server 2005.
Regards,
|||This 350 page document should keep you happy for a while (including "Upgrading replicated databases"):
http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en
Monday, March 12, 2012
migrate adp projects from SQL 7 to SQL 2000
We currently have a adp project linked with a Sql server 7 running NT4.
We need to replace old server with a win server 2003 with SQL 2000 sp4.
When I restore complete DB from old server to new server all objects
have (dbo) suffix and when we test the adp - through running a saved
report the report fails because it is looking for a table without the
(dbo) suffix.
Any help would be appreiciated.Not sure if I understand the question but ...
Are these linked tables? Just rename the links and that will work.
For example if the new link is dbo_Customers just rename it to Customers.
Please let us know if this was the issue or something else.
Ben Nevarez, MCDBA, OCP
Database Administrator
"dkordyban@.gmail.com" wrote:
> We currently have a adp project linked with a Sql server 7 running NT4.
> We need to replace old server with a win server 2003 with SQL 2000 sp4.
> When I restore complete DB from old server to new server all objects
> have (dbo) suffix and when we test the adp - through running a saved
> report the report fails because it is looking for a table without the
> (dbo) suffix.
> Any help would be appreiciated.
>|||Yes, SQL tables are linked to project. When viewing the tables, views
and stored procedures from the project, they all appear with (dbo)
after the object.
It may be somthing with sql 2000 sp4. I restored the exact same .bak
file to a Windows 2000 with sql 2000 sp3 and it worked fine - no (dbo)
after every object
Thanks for your time
We need to replace old server with a win server 2003 with SQL 2000 sp4.
When I restore complete DB from old server to new server all objects
have (dbo) suffix and when we test the adp - through running a saved
report the report fails because it is looking for a table without the
(dbo) suffix.
Any help would be appreiciated.Not sure if I understand the question but ...
Are these linked tables? Just rename the links and that will work.
For example if the new link is dbo_Customers just rename it to Customers.
Please let us know if this was the issue or something else.
Ben Nevarez, MCDBA, OCP
Database Administrator
"dkordyban@.gmail.com" wrote:
> We currently have a adp project linked with a Sql server 7 running NT4.
> We need to replace old server with a win server 2003 with SQL 2000 sp4.
> When I restore complete DB from old server to new server all objects
> have (dbo) suffix and when we test the adp - through running a saved
> report the report fails because it is looking for a table without the
> (dbo) suffix.
> Any help would be appreiciated.
>|||Yes, SQL tables are linked to project. When viewing the tables, views
and stored procedures from the project, they all appear with (dbo)
after the object.
It may be somthing with sql 2000 sp4. I restored the exact same .bak
file to a Windows 2000 with sql 2000 sp3 and it worked fine - no (dbo)
after every object
Thanks for your time
migrate adp projects from SQL 7 to SQL 2000
We currently have a adp project linked with a Sql server 7 running NT4.
We need to replace old server with a win server 2003 with SQL 2000 sp4.
When I restore complete DB from old server to new server all objects
have (dbo) suffix and when we test the adp - through running a saved
report the report fails because it is looking for a table without the
(dbo) suffix.
Any help would be appreiciated.
Not sure if I understand the question but ...
Are these linked tables? Just rename the links and that will work.
For example if the new link is dbo_Customers just rename it to Customers.
Please let us know if this was the issue or something else.
Ben Nevarez, MCDBA, OCP
Database Administrator
"dkordyban@.gmail.com" wrote:
> We currently have a adp project linked with a Sql server 7 running NT4.
> We need to replace old server with a win server 2003 with SQL 2000 sp4.
> When I restore complete DB from old server to new server all objects
> have (dbo) suffix and when we test the adp - through running a saved
> report the report fails because it is looking for a table without the
> (dbo) suffix.
> Any help would be appreiciated.
>
|||Yes, SQL tables are linked to project. When viewing the tables, views
and stored procedures from the project, they all appear with (dbo)
after the object.
It may be somthing with sql 2000 sp4. I restored the exact same .bak
file to a windows 2000 with sql 2000 sp3 and it worked fine - no (dbo)
after every object
Thanks for your time
We need to replace old server with a win server 2003 with SQL 2000 sp4.
When I restore complete DB from old server to new server all objects
have (dbo) suffix and when we test the adp - through running a saved
report the report fails because it is looking for a table without the
(dbo) suffix.
Any help would be appreiciated.
Not sure if I understand the question but ...
Are these linked tables? Just rename the links and that will work.
For example if the new link is dbo_Customers just rename it to Customers.
Please let us know if this was the issue or something else.
Ben Nevarez, MCDBA, OCP
Database Administrator
"dkordyban@.gmail.com" wrote:
> We currently have a adp project linked with a Sql server 7 running NT4.
> We need to replace old server with a win server 2003 with SQL 2000 sp4.
> When I restore complete DB from old server to new server all objects
> have (dbo) suffix and when we test the adp - through running a saved
> report the report fails because it is looking for a table without the
> (dbo) suffix.
> Any help would be appreiciated.
>
|||Yes, SQL tables are linked to project. When viewing the tables, views
and stored procedures from the project, they all appear with (dbo)
after the object.
It may be somthing with sql 2000 sp4. I restored the exact same .bak
file to a windows 2000 with sql 2000 sp3 and it worked fine - no (dbo)
after every object
Thanks for your time
migrate adp projects from SQL 7 to SQL 2000
We currently have a adp project linked with a Sql server 7 running NT4.
We need to replace old server with a win server 2003 with SQL 2000 sp4.
When I restore complete DB from old server to new server all objects
have (dbo) suffix and when we test the adp - through running a saved
report the report fails because it is looking for a table without the
(dbo) suffix.
Any help would be appreiciated.Not sure if I understand the question but ...
Are these linked tables? Just rename the links and that will work.
For example if the new link is dbo_Customers just rename it to Customers.
Please let us know if this was the issue or something else.
Ben Nevarez, MCDBA, OCP
Database Administrator
"dkordyban@.gmail.com" wrote:
> We currently have a adp project linked with a Sql server 7 running NT4.
> We need to replace old server with a win server 2003 with SQL 2000 sp4.
> When I restore complete DB from old server to new server all objects
> have (dbo) suffix and when we test the adp - through running a saved
> report the report fails because it is looking for a table without the
> (dbo) suffix.
> Any help would be appreiciated.
>|||Yes, SQL tables are linked to project. When viewing the tables, views
and stored procedures from the project, they all appear with (dbo)
after the object.
It may be somthing with sql 2000 sp4. I restored the exact same .bak
file to a windows 2000 with sql 2000 sp3 and it worked fine - no (dbo)
after every object
Thanks for your time
We need to replace old server with a win server 2003 with SQL 2000 sp4.
When I restore complete DB from old server to new server all objects
have (dbo) suffix and when we test the adp - through running a saved
report the report fails because it is looking for a table without the
(dbo) suffix.
Any help would be appreiciated.Not sure if I understand the question but ...
Are these linked tables? Just rename the links and that will work.
For example if the new link is dbo_Customers just rename it to Customers.
Please let us know if this was the issue or something else.
Ben Nevarez, MCDBA, OCP
Database Administrator
"dkordyban@.gmail.com" wrote:
> We currently have a adp project linked with a Sql server 7 running NT4.
> We need to replace old server with a win server 2003 with SQL 2000 sp4.
> When I restore complete DB from old server to new server all objects
> have (dbo) suffix and when we test the adp - through running a saved
> report the report fails because it is looking for a table without the
> (dbo) suffix.
> Any help would be appreiciated.
>|||Yes, SQL tables are linked to project. When viewing the tables, views
and stored procedures from the project, they all appear with (dbo)
after the object.
It may be somthing with sql 2000 sp4. I restored the exact same .bak
file to a windows 2000 with sql 2000 sp3 and it worked fine - no (dbo)
after every object
Thanks for your time
Monday, February 20, 2012
Microsoft SQL Server Management Studio
I have recently moved from a Microsoft SQL Server 2000 to a SQL Server
2005.
In the good old Enterprise Manager, when I imported a table from a SQL
server to another, I could choose "Copy objects and data between SQL
Server
databases". When choosen, all primary keys, and default values was
copied.
My question is:
Is it possible to do the same in Microsoft SQL Server Management Studio
with
SQL Server 2005? And how do I do it?
I have tried using the "SELECT * INTO NewTable FROM OldTable"
statement, but
it just drops all information about primary keys and default values.
Best Regards
Right click on the database in Object Explorer and choose "All Tasks". Then
choose export and follow the wizard.
Andrew J. Kelly SQL MVP
<pd@.acskive.dk> wrote in message
news:1143018478.487953.10000@.i40g2000cwc.googlegro ups.com...
>I have recently moved from a Microsoft SQL Server 2000 to a SQL Server
> 2005.
> In the good old Enterprise Manager, when I imported a table from a SQL
> server to another, I could choose "Copy objects and data between SQL
> Server
> databases". When choosen, all primary keys, and default values was
> copied.
> My question is:
> Is it possible to do the same in Microsoft SQL Server Management Studio
> with
> SQL Server 2005? And how do I do it?
> I have tried using the "SELECT * INTO NewTable FROM OldTable"
> statement, but
> it just drops all information about primary keys and default values.
>
> Best Regards
>
2005.
In the good old Enterprise Manager, when I imported a table from a SQL
server to another, I could choose "Copy objects and data between SQL
Server
databases". When choosen, all primary keys, and default values was
copied.
My question is:
Is it possible to do the same in Microsoft SQL Server Management Studio
with
SQL Server 2005? And how do I do it?
I have tried using the "SELECT * INTO NewTable FROM OldTable"
statement, but
it just drops all information about primary keys and default values.
Best Regards
Right click on the database in Object Explorer and choose "All Tasks". Then
choose export and follow the wizard.
Andrew J. Kelly SQL MVP
<pd@.acskive.dk> wrote in message
news:1143018478.487953.10000@.i40g2000cwc.googlegro ups.com...
>I have recently moved from a Microsoft SQL Server 2000 to a SQL Server
> 2005.
> In the good old Enterprise Manager, when I imported a table from a SQL
> server to another, I could choose "Copy objects and data between SQL
> Server
> databases". When choosen, all primary keys, and default values was
> copied.
> My question is:
> Is it possible to do the same in Microsoft SQL Server Management Studio
> with
> SQL Server 2005? And how do I do it?
> I have tried using the "SELECT * INTO NewTable FROM OldTable"
> statement, but
> it just drops all information about primary keys and default values.
>
> Best Regards
>
Subscribe to:
Posts (Atom)