copy from sqlsrv2000 to sqlsrv 7

Hi
Unfortunality have one of my clients sqlsrv 7 and whant to
remain to that version, how do I do to convert my
sqlsrv2000 databases to 7? Any good documentation/link
about that?
thanks!!
Staffan
Hi,
Due to architectural changes backup compatibility from SQL 2000 down to SQL
7 is not possible.
Only option is:-
1. Craete a database in SQL 7
2. Script out all the objects using Generate scripts in SQL 2000
3. Run and create the objects in SQL 7 database. ( Some script will fail if
you used new features of SQL 2000 like table data type...)
4. USE DTS to transfer the data from SQL 2000 to SQL 7 ( You can also use
BCP OUT from 2000 and BCP IN in sql 7)
Thanks
Hari
MCDBA
"Staffan" <anonymous@.discussions.microsoft.com> wrote in message
news:128f901c442d5$c58f8100$a101280a@.phx.gbl...
> Hi
> Unfortunality have one of my clients sqlsrv 7 and whant to
> remain to that version, how do I do to convert my
> sqlsrv2000 databases to 7? Any good documentation/link
> about that?
> thanks!!
> Staffan
|||Hi,
Due to architectural changes backup compatibility from SQL 2000 down to SQL
7 is not possible.
Only option is:-
1. Craete a database in SQL 7
2. Script out all the objects using Generate scripts in SQL 2000
3. Run and create the objects in SQL 7 database. ( Some script will fail if
you used new features of SQL 2000 like table data type...)
4. USE DTS to transfer the data from SQL 2000 to SQL 7 ( You can also use
BCP OUT from 2000 and BCP IN in sql 7)
Thanks
Hari
MCDBA
"Staffan" <anonymous@.discussions.microsoft.com> wrote in message
news:128f901c442d5$c58f8100$a101280a@.phx.gbl...
> Hi
> Unfortunality have one of my clients sqlsrv 7 and whant to
> remain to that version, how do I do to convert my
> sqlsrv2000 databases to 7? Any good documentation/link
> about that?
> thanks!!
> Staffan

copy from sqlsrv2000 to sqlsrv 7

Hi
Unfortunality have one of my clients sqlsrv 7 and whant to
remain to that version, how do I do to convert my
sqlsrv2000 databases to 7? Any good documentation/link
about that?
thanks!!
StaffanHi,
Due to architectural changes backup compatibility from SQL 2000 down to SQL
7 is not possible.
Only option is:-
1. Craete a database in SQL 7
2. Script out all the objects using Generate scripts in SQL 2000
3. Run and create the objects in SQL 7 database. ( Some script will fail if
you used new features of SQL 2000 like table data type...)
4. USE DTS to transfer the data from SQL 2000 to SQL 7 ( You can also use
BCP OUT from 2000 and BCP IN in sql 7)
Thanks
Hari
MCDBA
"Staffan" <anonymous@.discussions.microsoft.com> wrote in message
news:128f901c442d5$c58f8100$a101280a@.phx
.gbl...
> Hi
> Unfortunality have one of my clients sqlsrv 7 and whant to
> remain to that version, how do I do to convert my
> sqlsrv2000 databases to 7? Any good documentation/link
> about that?
> thanks!!
> Staffan|||Hi,
Due to architectural changes backup compatibility from SQL 2000 down to SQL
7 is not possible.
Only option is:-
1. Craete a database in SQL 7
2. Script out all the objects using Generate scripts in SQL 2000
3. Run and create the objects in SQL 7 database. ( Some script will fail if
you used new features of SQL 2000 like table data type...)
4. USE DTS to transfer the data from SQL 2000 to SQL 7 ( You can also use
BCP OUT from 2000 and BCP IN in sql 7)
Thanks
Hari
MCDBA
"Staffan" <anonymous@.discussions.microsoft.com> wrote in message
news:128f901c442d5$c58f8100$a101280a@.phx
.gbl...
> Hi
> Unfortunality have one of my clients sqlsrv 7 and whant to
> remain to that version, how do I do to convert my
> sqlsrv2000 databases to 7? Any good documentation/link
> about that?
> thanks!!
> Staffan

copy from sqlsrv2000 to sqlsrv 7

Hi
Unfortunality have one of my clients sqlsrv 7 and whant to
remain to that version, how do I do to convert my
sqlsrv2000 databases to 7? Any good documentation/link
about that?
thanks!!
StaffanHi,
Due to architectural changes backup compatibility from SQL 2000 down to SQL
7 is not possible.
Only option is:-
1. Craete a database in SQL 7
2. Script out all the objects using Generate scripts in SQL 2000
3. Run and create the objects in SQL 7 database. ( Some script will fail if
you used new features of SQL 2000 like table data type...)
4. USE DTS to transfer the data from SQL 2000 to SQL 7 ( You can also use
BCP OUT from 2000 and BCP IN in sql 7)
Thanks
Hari
MCDBA
"Staffan" <anonymous@.discussions.microsoft.com> wrote in message
news:128f901c442d5$c58f8100$a101280a@.phx.gbl...
> Hi
> Unfortunality have one of my clients sqlsrv 7 and whant to
> remain to that version, how do I do to convert my
> sqlsrv2000 databases to 7? Any good documentation/link
> about that?
> thanks!!
> Staffan|||Hi,
Due to architectural changes backup compatibility from SQL 2000 down to SQL
7 is not possible.
Only option is:-
1. Craete a database in SQL 7
2. Script out all the objects using Generate scripts in SQL 2000
3. Run and create the objects in SQL 7 database. ( Some script will fail if
you used new features of SQL 2000 like table data type...)
4. USE DTS to transfer the data from SQL 2000 to SQL 7 ( You can also use
BCP OUT from 2000 and BCP IN in sql 7)
Thanks
Hari
MCDBA
"Staffan" <anonymous@.discussions.microsoft.com> wrote in message
news:128f901c442d5$c58f8100$a101280a@.phx.gbl...
> Hi
> Unfortunality have one of my clients sqlsrv 7 and whant to
> remain to that version, how do I do to convert my
> sqlsrv2000 databases to 7? Any good documentation/link
> about that?
> thanks!!
> Staffan

Copy Database Wizard problem

Hi
Just a quick question: I often perform CDW from one server to the next as
part of clients server upgrades. All works fine:
The only major headache i am getting is that when i select the logins to be
copied as part of the CDW (including databases), the logins get copied
over, but their default database in the logins console is pointing to master
database and not the correct database compared to the old server? Sometimes
it works and sometimes it don't. I am not sure if i am doing anything
wrong.
Both servers are SQL 2000 inc SP3a using the same domain account. The
databases do not exist on the new server before the CDW.
Within the database itself, the alias Name has the correct assigned Login
Name
Can anyone give me some pointers?
Regards
J
Most likely you need to check to see if the dbid of the target databases are the same on both servers.
|||Ken
All dbid are the same, including same DBO and collation sort.
"Ken Dutton" <fj60landcruiser@.yahoo.com> wrote in message
news:22A8C534-A6D6-400C-BABB-22404154062A@.microsoft.com...
> Most likely you need to check to see if the dbid of the target databases
are the same on both servers.
|||This is documented in fhe following article:
PRB: The Copy Database Wizard Does Not Copy the Default Database
Information for Logins
http://support.microsoft.com/?id=331450
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Many thanks for link, this is just what i am looking for.
Thanks
J
"James" <hush@.dontspamme.com> wrote in message
news:uOW72LjQEHA.3732@.TK2MSFTNGP11.phx.gbl...
> Hi
> Just a quick question: I often perform CDW from one server to the next as
> part of clients server upgrades. All works fine:
> The only major headache i am getting is that when i select the logins to
be
> copied as part of the CDW (including databases), the logins get copied
> over, but their default database in the logins console is pointing to
master
> database and not the correct database compared to the old server?
Sometimes
> it works and sometimes it don't. I am not sure if i am doing anything
> wrong.
> Both servers are SQL 2000 inc SP3a using the same domain account. The
> databases do not exist on the new server before the CDW.
> Within the database itself, the alias Name has the correct assigned Login
> Name
> Can anyone give me some pointers?
> Regards
> J
>
>
sqlsql

Copy Database Wizard problem

Hi
Just a quick question: I often perform CDW from one server to the next as
part of clients server upgrades. All works fine:
The only major headache i am getting is that when i select the logins to be
copied as part of the CDW (including databases), the logins get copied
over, but their default database in the logins console is pointing to master
database and not the correct database compared to the old server? Sometimes
it works and sometimes it don't. I am not sure if i am doing anything
wrong.
Both servers are SQL 2000 inc SP3a using the same domain account. The
databases do not exist on the new server before the CDW.
Within the database itself, the alias Name has the correct assigned Login
Name
Can anyone give me some pointers?
Regards
JMost likely you need to check to see if the dbid of the target databases are the same on both servers.|||Ken
All dbid are the same, including same DBO and collation sort.
"Ken Dutton" <fj60landcruiser@.yahoo.com> wrote in message
news:22A8C534-A6D6-400C-BABB-22404154062A@.microsoft.com...
> Most likely you need to check to see if the dbid of the target databases
are the same on both servers.|||This is documented in fhe following article:
PRB: The Copy Database Wizard Does Not Copy the Default Database
Information for Logins
http://support.microsoft.com/?id=331450
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Many thanks for link, this is just what i am looking for.
Thanks
J
"James" <hush@.dontspamme.com> wrote in message
news:uOW72LjQEHA.3732@.TK2MSFTNGP11.phx.gbl...
> Hi
> Just a quick question: I often perform CDW from one server to the next as
> part of clients server upgrades. All works fine:
> The only major headache i am getting is that when i select the logins to
be
> copied as part of the CDW (including databases), the logins get copied
> over, but their default database in the logins console is pointing to
master
> database and not the correct database compared to the old server?
Sometimes
> it works and sometimes it don't. I am not sure if i am doing anything
> wrong.
> Both servers are SQL 2000 inc SP3a using the same domain account. The
> databases do not exist on the new server before the CDW.
> Within the database itself, the alias Name has the correct assigned Login
> Name
> Can anyone give me some pointers?
> Regards
> J
>
>

Copy Database Wizard problem

Hi
Just a quick question: I often perform CDW from one server to the next as
part of clients server upgrades. All works fine:
The only major headache i am getting is that when i select the logins to be
copied as part of the CDW (including databases), the logins get copied
over, but their default database in the logins console is pointing to master
database and not the correct database compared to the old server? Sometimes
it works and sometimes it don't. I am not sure if i am doing anything
wrong.
Both servers are SQL 2000 inc SP3a using the same domain account. The
databases do not exist on the new server before the CDW.
Within the database itself, the alias Name has the correct assigned Login
Name
Can anyone give me some pointers?
Regards
JMost likely you need to check to see if the dbid of the target databases are
the same on both servers.|||Ken
All dbid are the same, including same DBO and collation sort.
"Ken Dutton" <fj60landcruiser@.yahoo.com> wrote in message
news:22A8C534-A6D6-400C-BABB-22404154062A@.microsoft.com...
> Most likely you need to check to see if the dbid of the target databases
are the same on both servers.|||This is documented in fhe following article:
PRB: The Copy Database Wizard Does Not Copy the Default Database
Information for Logins
http://support.microsoft.com/?id=331450
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Many thanks for link, this is just what i am looking for.
Thanks
J
"James" <hush@.dontspamme.com> wrote in message
news:uOW72LjQEHA.3732@.TK2MSFTNGP11.phx.gbl...
> Hi
> Just a quick question: I often perform CDW from one server to the next as
> part of clients server upgrades. All works fine:
> The only major headache i am getting is that when i select the logins to
be
> copied as part of the CDW (including databases), the logins get copied
> over, but their default database in the logins console is pointing to
master
> database and not the correct database compared to the old server?
Sometimes
> it works and sometimes it don't. I am not sure if i am doing anything
> wrong.
> Both servers are SQL 2000 inc SP3a using the same domain account. The
> databases do not exist on the new server before the CDW.
> Within the database itself, the alias Name has the correct assigned Login
> Name
> Can anyone give me some pointers?
> Regards
> J
>
>

Converting to use replication

I have a DB running under SQL 2005. I would like to enable the database for
replication to offline clients (SQLExpress) and SQL Server 2005 Compact
Edition.
Will converting the primary keys of the database to use GUID's be sufficient
to enable the replication to work property.? They are currently integers.
No, don't do this. Replication will add its own GUID key.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Nick Zdunic" <NickZdunic@.discussions.microsoft.com> wrote in message
news:A04F975C-AC8F-4FDB-A6D4-030C21392DFF@.microsoft.com...
>I have a DB running under SQL 2005. I would like to enable the database
>for
> replication to offline clients (SQLExpress) and SQL Server 2005 Compact
> Edition.
> Will converting the primary keys of the database to use GUID's be
> sufficient
> to enable the replication to work property.? They are currently integers.
|||I know that it does this, but my keys are autonumber fields, so wouldn't it
be better to convert them to GUIDs so that clashes don't occur later on.
Because the fields are GUIDs SQL server shouldn't need to add GUIDs - or
will this still occur even when GUIDs are already present?
"Hilary Cotter" wrote:

> No, don't do this. Replication will add its own GUID key.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Nick Zdunic" <NickZdunic@.discussions.microsoft.com> wrote in message
> news:A04F975C-AC8F-4FDB-A6D4-030C21392DFF@.microsoft.com...
>
>
|||Either consider automatic identity range management or use different seeds
on either side, i.e. even on one side, odd on another.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Nick Zdunic" <NickZdunic@.discussions.microsoft.com> wrote in message
news:EEEEBE0A-22E9-432A-A2AF-98EF18806B7A@.microsoft.com...[vbcol=seagreen]
>I know that it does this, but my keys are autonumber fields, so wouldn't it
> be better to convert them to GUIDs so that clashes don't occur later on.
> Because the fields are GUIDs SQL server shouldn't need to add GUIDs - or
> will this still occur even when GUIDs are already present?
> "Hilary Cotter" wrote:
|||Might still go with GUIDs - as the number of clients could vary so it will be
easier to manage.
So will using GUIDs stop the extra GUID being added by SQL Server?
"Hilary Cotter" wrote:

> Either consider automatic identity range management or use different seeds
> on either side, i.e. even on one side, odd on another.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Nick Zdunic" <NickZdunic@.discussions.microsoft.com> wrote in message
> news:EEEEBE0A-22E9-432A-A2AF-98EF18806B7A@.microsoft.com...
>
>
|||You can add your own GUID field and call it what you want. Replication
needs a uniqueidentifier field with the ROWGUIDCOL property set. If it
finds an existing one it will use that instead of creating a new one.
Just remember to set the field default to (newid()).
I agree with the advice not to set your primary key to a GUID. You will
run into performance problems when the table grows. Searching an integer
index is much faster than searching an GUID index. Auto identity
requires management, but it is definately the way to go.
Nick Zdunic wrote:[vbcol=seagreen]
> Might still go with GUIDs - as the number of clients could vary so it will be
> easier to manage.
> So will using GUIDs stop the extra GUID being added by SQL Server?
> "Hilary Cotter" wrote:
|||Int's will be faster, but with more than 5 replicas and maybe even 10 to 50
managing autonumber fields would be a nightmare.
"JE" wrote:

> You can add your own GUID field and call it what you want. Replication
> needs a uniqueidentifier field with the ROWGUIDCOL property set. If it
> finds an existing one it will use that instead of creating a new one.
> Just remember to set the field default to (newid()).
> I agree with the advice not to set your primary key to a GUID. You will
> run into performance problems when the table grows. Searching an integer
> index is much faster than searching an GUID index. Auto identity
> requires management, but it is definately the way to go.
>
> Nick Zdunic wrote:
>