Showing posts with label upgrade. Show all posts
Showing posts with label upgrade. Show all posts

Monday, March 19, 2012

90 compatability mode option not available after upgrade

I upgrade to sql 2005 from sql2000. The problem is that the compatability mode 90 is not available, 8.0 and 7.0 are, when looking at the compatability level in the properties tab. THe GUI, Management studio is loaded and operational.

What do I need to do to make the 90 compatability mode available?

Thanks!

You can use the following T-SQL Sentences to change to Compatibility Mode to 90 for your database.

USE [master]

GO

EXEC dbo.sp_dbcmptlevel @.dbname=N'MyDatabase', @.new_cmptlevel=90

GO

But, i'm sure that this will not work fine for you, because, i look that is possible that your database have enabled some features, that only work in the 80 compatibility mode, because this has been disabled or are obsolete in SQL Server 2005.

Best Regards,

|||

Are you sure you actually installed the 2005 database engine? It sounds as if just the client tools are installed. What version number is reported when you run the following SQL against the master database?

SELECT @.@.version

837 patch and MS03-031

Hello
We're about to apply the MS03-031 security rollup patch to upgrade our 90
SQL Servers from SP3a (760) to (818).
Problem is we have applied a hotfix already to a couple of boxes which
ugraded SQL to version (837).
What will happen when we apply MS03-031 to these boxes with the hotfix? Will
it fail and if so whats the solution?
thank you
-- cranfield, DBA
Hi
It will run, but is clever enough not to run older scripts against the newer
build. It does binary file version checking so it won't overwrite newer
binaries.
Have you considered hotfix 878?
When I tried to run 818 against a 952 server, I got the following:
=== Version check on sqlservr.exe 8.0.952 shows different major build of
sqlservr.exe than hotfix build number 8.00.818
=== NOT RUNNING SCRIPTS
The build number of SQLSERVR.EXE and HotFix package did not match. This
happens
when SQLSERVR.EXE was not replaced because the version was higher than the
Hotfix build.
In these cases Hotfix will not run any scripts and return error code
ERROR_BAD_ENVIRONMENT
Error message: Error running SQL script. Please view the log file for details.
INSTALL FAILURE: Hotfix failed to apply the patches on instance MSSQLSERVER,
the error code returned was: 10
<EndFunc Name='DoSQLHotFix' Return='10' GetLastError='0'>
Regards
Mike
"cranfield" wrote:

> Hello
> We're about to apply the MS03-031 security rollup patch to upgrade our 90
> SQL Servers from SP3a (760) to (818).
> Problem is we have applied a hotfix already to a couple of boxes which
> ugraded SQL to version (837).
> What will happen when we apply MS03-031 to these boxes with the hotfix? Will
> it fail and if so whats the solution?
> thank you
> -- cranfield, DBA
|||Hi Mike
Why do you ask if I have considered hotfix 878? We applied the 837 hotfix i
an attempt to sort out some Exception errors we were having on our 4-node
cluster.
We're just looking at bringing up our servers to an accepted level and our
testers have only tested up to 818, MS02-031.
regards
Alan Cranfield
DBA Support
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> It will run, but is clever enough not to run older scripts against the newer
> build. It does binary file version checking so it won't overwrite newer
> binaries.
> Have you considered hotfix 878?
> When I tried to run 818 against a 952 server, I got the following:
> === Version check on sqlservr.exe 8.0.952 shows different major build of
> sqlservr.exe than hotfix build number 8.00.818
>
> === NOT RUNNING SCRIPTS
> The build number of SQLSERVR.EXE and HotFix package did not match. This
> happens
> when SQLSERVR.EXE was not replaced because the version was higher than the
> Hotfix build.
> In these cases Hotfix will not run any scripts and return error code
> ERROR_BAD_ENVIRONMENT
> Error message: Error running SQL script. Please view the log file for details.
> INSTALL FAILURE: Hotfix failed to apply the patches on instance MSSQLSERVER,
> the error code returned was: 10
> <EndFunc Name='DoSQLHotFix' Return='10' GetLastError='0'>
> Regards
> Mike
> "cranfield" wrote:
|||Hi
878 is the highest publicly available hotfix, that is fully supported by PSS.
We encountered quite a few problems with hotfixes in the 820 to 850 range,
and those issues were fixed after 850.
(regression bugs etc)
Regards
Mike
"Cranfield" wrote:
[vbcol=seagreen]
> Hi Mike
> Why do you ask if I have considered hotfix 878? We applied the 837 hotfix i
> an attempt to sort out some Exception errors we were having on our 4-node
> cluster.
> We're just looking at bringing up our servers to an accepted level and our
> testers have only tested up to 818, MS02-031.
> regards
> Alan Cranfield
> DBA Support
> "Mike Epprecht (SQL MVP)" wrote:
|||I suspect applying MS03-031 to the servers that are already at
8.00.837 will do nothing - it shouldn't overwrite files with
earlier versions, and you can compare the file information in the KB
article http://support.microsoft.com/kb/821277 with what's on your
servers.
Is there a reason you think MS03-31 contains something that is
not already installed as part of the 837 hotfix on the hotfixed boxes?
Usually these things are cumulative, and especially since 818 was a
security issue, I'd be surprised if MSFT gave out something numbered
8.00.837 that didn't fix prior security issues.
Steve Kass
Drew University
cranfield wrote:

>Hello
>We're about to apply the MS03-031 security rollup patch to upgrade our 90
>SQL Servers from SP3a (760) to (818).
>Problem is we have applied a hotfix already to a couple of boxes which
>ugraded SQL to version (837).
>What will happen when we apply MS03-031 to these boxes with the hotfix? Will
>it fail and if so whats the solution?
>thank you
>-- cranfield, DBA
>
|||This is exactly what i want to know. Can I safely assume that I don't have to
patch the 837 servers as they will already be up to 818 level?
thanks
alan
"Steve Kass" wrote:

> I suspect applying MS03-031 to the servers that are already at
> 8.00.837 will do nothing - it shouldn't overwrite files with
> earlier versions, and you can compare the file information in the KB
> article http://support.microsoft.com/kb/821277 with what's on your
> servers.
> Is there a reason you think MS03-31 contains something that is
> not already installed as part of the 837 hotfix on the hotfixed boxes?
> Usually these things are cumulative, and especially since 818 was a
> security issue, I'd be surprised if MSFT gave out something numbered
> 8.00.837 that didn't fix prior security issues.
> Steve Kass
> Drew University
> cranfield wrote:
>

837 patch and MS03-031

Hello
We're about to apply the MS03-031 security rollup patch to upgrade our 90
SQL Servers from SP3a (760) to (818).
Problem is we have applied a hotfix already to a couple of boxes which
ugraded SQL to version (837).
What will happen when we apply MS03-031 to these boxes with the hotfix? Will
it fail and if so whats the solution?
thank you
-- cranfield, DBAHi
It will run, but is clever enough not to run older scripts against the newer
build. It does binary file version checking so it won't overwrite newer
binaries.
Have you considered hotfix 878?
When I tried to run 818 against a 952 server, I got the following:
=== Version check on sqlservr.exe 8.0.952 shows different major build of
sqlservr.exe than hotfix build number 8.00.818
=== NOT RUNNING SCRIPTS
The build number of SQLSERVR.EXE and HotFix package did not match. This
happens
when SQLSERVR.EXE was not replaced because the version was higher than the
Hotfix build.
In these cases Hotfix will not run any scripts and return error code
ERROR_BAD_ENVIRONMENT
Error message: Error running SQL script. Please view the log file for detail
s.
INSTALL FAILURE: Hotfix failed to apply the patches on instance MSSQLSERVER,
the error code returned was: 10
<EndFunc Name='DoSQLHotFix' Return='10' GetLastError='0'>
Regards
Mike
"cranfield" wrote:

> Hello
> We're about to apply the MS03-031 security rollup patch to upgrade our 90
> SQL Servers from SP3a (760) to (818).
> Problem is we have applied a hotfix already to a couple of boxes which
> ugraded SQL to version (837).
> What will happen when we apply MS03-031 to these boxes with the hotfix? Wi
ll
> it fail and if so whats the solution?
> thank you
> -- cranfield, DBA|||Hi Mike
Why do you ask if I have considered hotfix 878? We applied the 837 hotfix i
an attempt to sort out some Exception errors we were having on our 4-node
cluster.
We're just looking at bringing up our servers to an accepted level and our
testers have only tested up to 818, MS02-031.
regards
Alan Cranfield
DBA Support
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> It will run, but is clever enough not to run older scripts against the new
er
> build. It does binary file version checking so it won't overwrite newer
> binaries.
> Have you considered hotfix 878?
> When I tried to run 818 against a 952 server, I got the following:
> === Version check on sqlservr.exe 8.0.952 shows different major build of
> sqlservr.exe than hotfix build number 8.00.818
>
> === NOT RUNNING SCRIPTS
> The build number of SQLSERVR.EXE and HotFix package did not match. This
> happens
> when SQLSERVR.EXE was not replaced because the version was higher than the
> Hotfix build.
> In these cases Hotfix will not run any scripts and return error code
> ERROR_BAD_ENVIRONMENT
> Error message: Error running SQL script. Please view the log file for deta
ils.
> INSTALL FAILURE: Hotfix failed to apply the patches on instance MSSQLSERVE
R,
> the error code returned was: 10
> <EndFunc Name='DoSQLHotFix' Return='10' GetLastError='0'>
> Regards
> Mike
> "cranfield" wrote:
>|||Hi
878 is the highest publicly available hotfix, that is fully supported by PSS
.
We encountered quite a few problems with hotfixes in the 820 to 850 range,
and those issues were fixed after 850.
(regression bugs etc)
Regards
Mike
"Cranfield" wrote:
[vbcol=seagreen]
> Hi Mike
> Why do you ask if I have considered hotfix 878? We applied the 837 hotfix
i
> an attempt to sort out some Exception errors we were having on our 4-node
> cluster.
> We're just looking at bringing up our servers to an accepted level and our
> testers have only tested up to 818, MS02-031.
> regards
> Alan Cranfield
> DBA Support
> "Mike Epprecht (SQL MVP)" wrote:
>|||I suspect applying MS03-031 to the servers that are already at
8.00.837 will do nothing - it shouldn't overwrite files with
earlier versions, and you can compare the file information in the KB
article http://support.microsoft.com/kb/821277 with what's on your
servers.
Is there a reason you think MS03-31 contains something that is
not already installed as part of the 837 hotfix on the hotfixed boxes?
Usually these things are cumulative, and especially since 818 was a
security issue, I'd be surprised if MSFT gave out something numbered
8.00.837 that didn't fix prior security issues.
Steve Kass
Drew University
cranfield wrote:

>Hello
>We're about to apply the MS03-031 security rollup patch to upgrade our 90
>SQL Servers from SP3a (760) to (818).
>Problem is we have applied a hotfix already to a couple of boxes which
>ugraded SQL to version (837).
>What will happen when we apply MS03-031 to these boxes with the hotfix? Wil
l
>it fail and if so whats the solution?
>thank you
>-- cranfield, DBA
>|||This is exactly what i want to know. Can I safely assume that I don't have t
o
patch the 837 servers as they will already be up to 818 level?
thanks
alan
"Steve Kass" wrote:

> I suspect applying MS03-031 to the servers that are already at
> 8.00.837 will do nothing - it shouldn't overwrite files with
> earlier versions, and you can compare the file information in the KB
> article http://support.microsoft.com/kb/821277 with what's on your
> servers.
> Is there a reason you think MS03-31 contains something that is
> not already installed as part of the 837 hotfix on the hotfixed boxes?
> Usually these things are cumulative, and especially since 818 was a
> security issue, I'd be surprised if MSFT gave out something numbered
> 8.00.837 that didn't fix prior security issues.
> Steve Kass
> Drew University
> cranfield wrote:
>
>

837 patch and MS03-031

Hello
We're about to apply the MS03-031 security rollup patch to upgrade our 90
SQL Servers from SP3a (760) to (818).
Problem is we have applied a hotfix already to a couple of boxes which
ugraded SQL to version (837).
What will happen when we apply MS03-031 to these boxes with the hotfix? Will
it fail and if so whats the solution?
thank you
-- cranfield, DBAHi
It will run, but is clever enough not to run older scripts against the newer
build. It does binary file version checking so it won't overwrite newer
binaries.
Have you considered hotfix 878?
When I tried to run 818 against a 952 server, I got the following:
=== Version check on sqlservr.exe 8.0.952 shows different major build of
sqlservr.exe than hotfix build number 8.00.818
=== NOT RUNNING SCRIPTS
The build number of SQLSERVR.EXE and HotFix package did not match. This
happens
when SQLSERVR.EXE was not replaced because the version was higher than the
Hotfix build.
In these cases Hotfix will not run any scripts and return error code
ERROR_BAD_ENVIRONMENT
Error message: Error running SQL script. Please view the log file for details.
INSTALL FAILURE: Hotfix failed to apply the patches on instance MSSQLSERVER,
the error code returned was: 10
<EndFunc Name='DoSQLHotFix' Return='10' GetLastError='0'>
Regards
Mike
"cranfield" wrote:
> Hello
> We're about to apply the MS03-031 security rollup patch to upgrade our 90
> SQL Servers from SP3a (760) to (818).
> Problem is we have applied a hotfix already to a couple of boxes which
> ugraded SQL to version (837).
> What will happen when we apply MS03-031 to these boxes with the hotfix? Will
> it fail and if so whats the solution?
> thank you
> -- cranfield, DBA|||Hi Mike
Why do you ask if I have considered hotfix 878? We applied the 837 hotfix i
an attempt to sort out some Exception errors we were having on our 4-node
cluster.
We're just looking at bringing up our servers to an accepted level and our
testers have only tested up to 818, MS02-031.
regards
Alan Cranfield
DBA Support
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> It will run, but is clever enough not to run older scripts against the newer
> build. It does binary file version checking so it won't overwrite newer
> binaries.
> Have you considered hotfix 878?
> When I tried to run 818 against a 952 server, I got the following:
> === Version check on sqlservr.exe 8.0.952 shows different major build of
> sqlservr.exe than hotfix build number 8.00.818
>
> === NOT RUNNING SCRIPTS
> The build number of SQLSERVR.EXE and HotFix package did not match. This
> happens
> when SQLSERVR.EXE was not replaced because the version was higher than the
> Hotfix build.
> In these cases Hotfix will not run any scripts and return error code
> ERROR_BAD_ENVIRONMENT
> Error message: Error running SQL script. Please view the log file for details.
> INSTALL FAILURE: Hotfix failed to apply the patches on instance MSSQLSERVER,
> the error code returned was: 10
> <EndFunc Name='DoSQLHotFix' Return='10' GetLastError='0'>
> Regards
> Mike
> "cranfield" wrote:
> > Hello
> >
> > We're about to apply the MS03-031 security rollup patch to upgrade our 90
> > SQL Servers from SP3a (760) to (818).
> >
> > Problem is we have applied a hotfix already to a couple of boxes which
> > ugraded SQL to version (837).
> >
> > What will happen when we apply MS03-031 to these boxes with the hotfix? Will
> > it fail and if so whats the solution?
> >
> > thank you
> >
> > -- cranfield, DBA|||Hi
878 is the highest publicly available hotfix, that is fully supported by PSS.
We encountered quite a few problems with hotfixes in the 820 to 850 range,
and those issues were fixed after 850.
(regression bugs etc)
Regards
Mike
"Cranfield" wrote:
> Hi Mike
> Why do you ask if I have considered hotfix 878? We applied the 837 hotfix i
> an attempt to sort out some Exception errors we were having on our 4-node
> cluster.
> We're just looking at bringing up our servers to an accepted level and our
> testers have only tested up to 818, MS02-031.
> regards
> Alan Cranfield
> DBA Support
> "Mike Epprecht (SQL MVP)" wrote:
> > Hi
> >
> > It will run, but is clever enough not to run older scripts against the newer
> > build. It does binary file version checking so it won't overwrite newer
> > binaries.
> >
> > Have you considered hotfix 878?
> >
> > When I tried to run 818 against a 952 server, I got the following:
> >
> > === Version check on sqlservr.exe 8.0.952 shows different major build of
> > sqlservr.exe than hotfix build number 8.00.818
> >
> >
> > === NOT RUNNING SCRIPTS
> > The build number of SQLSERVR.EXE and HotFix package did not match. This
> > happens
> > when SQLSERVR.EXE was not replaced because the version was higher than the
> > Hotfix build.
> > In these cases Hotfix will not run any scripts and return error code
> > ERROR_BAD_ENVIRONMENT
> >
> > Error message: Error running SQL script. Please view the log file for details.
> > INSTALL FAILURE: Hotfix failed to apply the patches on instance MSSQLSERVER,
> > the error code returned was: 10
> > <EndFunc Name='DoSQLHotFix' Return='10' GetLastError='0'>
> >
> > Regards
> > Mike
> >
> > "cranfield" wrote:
> >
> > > Hello
> > >
> > > We're about to apply the MS03-031 security rollup patch to upgrade our 90
> > > SQL Servers from SP3a (760) to (818).
> > >
> > > Problem is we have applied a hotfix already to a couple of boxes which
> > > ugraded SQL to version (837).
> > >
> > > What will happen when we apply MS03-031 to these boxes with the hotfix? Will
> > > it fail and if so whats the solution?
> > >
> > > thank you
> > >
> > > -- cranfield, DBA|||I suspect applying MS03-031 to the servers that are already at
8.00.837 will do nothing - it shouldn't overwrite files with
earlier versions, and you can compare the file information in the KB
article http://support.microsoft.com/kb/821277 with what's on your
servers.
Is there a reason you think MS03-31 contains something that is
not already installed as part of the 837 hotfix on the hotfixed boxes?
Usually these things are cumulative, and especially since 818 was a
security issue, I'd be surprised if MSFT gave out something numbered
8.00.837 that didn't fix prior security issues.
Steve Kass
Drew University
cranfield wrote:
>Hello
>We're about to apply the MS03-031 security rollup patch to upgrade our 90
>SQL Servers from SP3a (760) to (818).
>Problem is we have applied a hotfix already to a couple of boxes which
>ugraded SQL to version (837).
>What will happen when we apply MS03-031 to these boxes with the hotfix? Will
>it fail and if so whats the solution?
>thank you
>-- cranfield, DBA
>|||This is exactly what i want to know. Can I safely assume that I don't have to
patch the 837 servers as they will already be up to 818 level?
thanks
alan
"Steve Kass" wrote:
> I suspect applying MS03-031 to the servers that are already at
> 8.00.837 will do nothing - it shouldn't overwrite files with
> earlier versions, and you can compare the file information in the KB
> article http://support.microsoft.com/kb/821277 with what's on your
> servers.
> Is there a reason you think MS03-31 contains something that is
> not already installed as part of the 837 hotfix on the hotfixed boxes?
> Usually these things are cumulative, and especially since 818 was a
> security issue, I'd be surprised if MSFT gave out something numbered
> 8.00.837 that didn't fix prior security issues.
> Steve Kass
> Drew University
> cranfield wrote:
> >Hello
> >
> >We're about to apply the MS03-031 security rollup patch to upgrade our 90
> >SQL Servers from SP3a (760) to (818).
> >
> >Problem is we have applied a hotfix already to a couple of boxes which
> >ugraded SQL to version (837).
> >
> >What will happen when we apply MS03-031 to these boxes with the hotfix? Will
> >it fail and if so whats the solution?
> >
> >thank you
> >
> >-- cranfield, DBA
> >
> >
>

Sunday, March 11, 2012

8000 char Row limit

is the 8000 char row limit only an issue in standard
edition? If I upgrade to enterprise edition will I not
have this problem? Thanks.
It has nothing to do with the edition; it is a storage / engine limitation.
What exactly are you trying to do? Are you aware of the reasons for the
limit?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.
|||The actual row limit is 8060, and the max char/varchar column size is 8000
bytes.
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.
|||This sql server is running our Microsoft CRM database. I
am trying to create some custom attributes. When I try to
create one it says that I am at the 8000 char row limit.
I can not delete any attributes. Is there not a way
around this? Thanks for your replys.

>--Original Message--
>It has nothing to do with the edition; it is a storage /
engine limitation.
>What exactly are you trying to do? Are you aware of the
reasons for the
>limit?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
>news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
>
>.
>
|||Is there any way around the 8000 byte limit?

>--Original Message--
>The actual row limit is 8060, and the max char/varchar
column size is 8000
>bytes.
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
>news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
>
>.
>
|||The error message is just a warning. You can go ahead and create a table
that is wider, just don't expect to use it all. For example:
CREATE TABLE dbo.blat
(
bar1 VARCHAR(5000),
bar2 VARCHAR(5000)
)
GO
Warning: The table 'blat' has been created but its maximum row size (10025)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a
row in this table will fail if the resulting row length exceeds 8060 bytes.
As the message states, the table was still created. However, populating it
with data will be more challenging. These work fine:
INSERT blat SELECT 'a', 'b'
INSERT blat SELECT REPLICATE('a', 5000), 'b'
INSERT blat SELECT 'a', REPLICATE('b', 5000)
But when you try and send more than 8060 bytes, you will have problems, e.g.
INSERT blat SELECT
REPLICATE('a', 5000), REPLICATE('b', 5000)
You get:
Server: Msg 511, Level 16, State 1, Line 1
Cannot create a row of size 10013 which is greater than the allowable
maximum of 8060.
The statement has been terminated.
What I recommend is storing any larger attributes in a separate table and
use relationships for data integrity.
Maybe you can show the code that represents "when I try to create one" and
the ACTUAL error message you receive, not your casual interpretation...
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189ae01c420b2$c7d24410$a601280a@.phx.gbl...
> This sql server is running our Microsoft CRM database. I
> am trying to create some custom attributes. When I try to
> create one it says that I am at the 8000 char row limit.
> I can not delete any attributes. Is there not a way
> around this? Thanks for your replys.
|||I am not trying to manually create this table. The table
is created upon the installation of CRM and I am trying to
add an attribute to it within microsoft CRM. In CRM i get
the following error:
An error occurred during the addition of the new field.
The addition failed. For more information, see the event
log.
Event log error:
1.
dmLog: Failed to add new Picklist attribute (CFPcatagory)
to Account entity.
2.
dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
bytes.
I dont know if you are familiar with CRM deployment
manager, there is a section to create mappings, which
might be the same as the relationships as your talking
about. It will not let me modify any existing attribute,
even the ones that I have created. I cant delete an
attribute either.
Thanks again for your help.

>--Original Message--
>The error message is just a warning. You can go ahead
and create a table
>that is wider, just don't expect to use it all. For
example:
>CREATE TABLE dbo.blat
>(
> bar1 VARCHAR(5000),
> bar2 VARCHAR(5000)
>)
>GO
>Warning: The table 'blat' has been created but its
maximum row size (10025)
>exceeds the maximum number of bytes per row (8060).
INSERT or UPDATE of a
>row in this table will fail if the resulting row length
exceeds 8060 bytes.
>As the message states, the table was still created.
However, populating it
>with data will be more challenging. These work fine:
>INSERT blat SELECT 'a', 'b'
>INSERT blat SELECT REPLICATE('a', 5000), 'b'
>INSERT blat SELECT 'a', REPLICATE('b', 5000)
>But when you try and send more than 8060 bytes, you will
have problems, e.g.
>INSERT blat SELECT
> REPLICATE('a', 5000), REPLICATE('b', 5000)
>You get:
>Server: Msg 511, Level 16, State 1, Line 1
>Cannot create a row of size 10013 which is greater than
the allowable
>maximum of 8060.
>The statement has been terminated.
>What I recommend is storing any larger attributes in a
separate table and
>use relationships for data integrity.
>Maybe you can show the code that represents "when I try
to create one" and
>the ACTUAL error message you receive, not your casual
interpretation...
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"billy dodson" <billy@.pmicromart.com> wrote in message
>news:189ae01c420b2$c7d24410$a601280a@.phx.gbl...
I
to
>
>.
>
|||This limitation will be removed in Yukon. You will be able to do the
following (for example):
create table t1 (c1 varchar (5000), c2 varchar (5000))
go
insert into t1 values (replicate ('a', 5000), replicate ('b', 5000))
go
with no problems.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx.gbl...
> Is there any way around the 8000 byte limit?
> column size is 8000
|||Billy,
As stated, it is only a warning. How much of the 8060 char limit is being
used by the unmodified table?
If you have 16 bytes left, you can assign the new attribute to a text or
ntext column, and that will fit. Of course, you then have to deal with the
issues that arise from using text columns.
You can create an attribute table of nothing more than an identity or guid
column and the attribute and then just store the identity (4 bytes) or
rowguid (16 bytes) in your table.
You might also run statistics on the actual size of data being stored vs the
field size for all fields in the table. Knowing this will give you an idea
of how much space you can "safely" assign to the new attribute. The caveat
here is that you will have to check the length of everything on inserts and
updates.
Regards,
John
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx.gbl...[color=darkblue]
> Is there any way around the 8000 byte limit?
> column size is 8000
|||sounds like one for the CRM group if there is one - being unable to remove
user-defined attributes sounds like a design flaw
Niall Litchfield
Oracle DBA
Audit Commission UK
http://www.niall.litchfield.dial.pipex.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:1bad601c420b8$297548c0$a101280a@.phx.gbl...[vbcol=seagreen]
> I am not trying to manually create this table. The table
> is created upon the installation of CRM and I am trying to
> add an attribute to it within microsoft CRM. In CRM i get
> the following error:
> An error occurred during the addition of the new field.
> The addition failed. For more information, see the event
> log.
> Event log error:
> 1.
> dmLog: Failed to add new Picklist attribute (CFPcatagory)
> to Account entity.
> 2.
> dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
> B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
> bytes.
>
> I dont know if you are familiar with CRM deployment
> manager, there is a section to create mappings, which
> might be the same as the relationships as your talking
> about. It will not let me modify any existing attribute,
> even the ones that I have created. I cant delete an
> attribute either.
> Thanks again for your help.
>
> and create a table
> example:
> maximum row size (10025)
> INSERT or UPDATE of a
> exceeds 8060 bytes.
> However, populating it
> have problems, e.g.
> the allowable
> separate table and
> to create one" and
> interpretation...
> I
> to

8000 char Row limit

is the 8000 char row limit only an issue in standard
edition? If I upgrade to enterprise edition will I not
have this problem? Thanks.It has nothing to do with the edition; it is a storage / engine limitation.
What exactly are you trying to do? Are you aware of the reasons for the
limit?
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.|||The actual row limit is 8060, and the max char/varchar column size is 8000
bytes.
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.|||This sql server is running our Microsoft CRM database. I
am trying to create some custom attributes. When I try to
create one it says that I am at the 8000 char row limit.
I can not delete any attributes. Is there not a way
around this? Thanks for your replys.
>--Original Message--
>It has nothing to do with the edition; it is a storage /
engine limitation.
>What exactly are you trying to do? Are you aware of the
reasons for the
>limit?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
>news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
>> is the 8000 char row limit only an issue in standard
>> edition? If I upgrade to enterprise edition will I not
>> have this problem? Thanks.
>
>.
>|||Is there any way around the 8000 byte limit?
>--Original Message--
>The actual row limit is 8060, and the max char/varchar
column size is 8000
>bytes.
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
>news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
>> is the 8000 char row limit only an issue in standard
>> edition? If I upgrade to enterprise edition will I not
>> have this problem? Thanks.
>
>.
>|||The error message is just a warning. You can go ahead and create a table
that is wider, just don't expect to use it all. For example:
CREATE TABLE dbo.blat
(
bar1 VARCHAR(5000),
bar2 VARCHAR(5000)
)
GO
Warning: The table 'blat' has been created but its maximum row size (10025)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a
row in this table will fail if the resulting row length exceeds 8060 bytes.
As the message states, the table was still created. However, populating it
with data will be more challenging. These work fine:
INSERT blat SELECT 'a', 'b'
INSERT blat SELECT REPLICATE('a', 5000), 'b'
INSERT blat SELECT 'a', REPLICATE('b', 5000)
But when you try and send more than 8060 bytes, you will have problems, e.g.
INSERT blat SELECT
REPLICATE('a', 5000), REPLICATE('b', 5000)
You get:
Server: Msg 511, Level 16, State 1, Line 1
Cannot create a row of size 10013 which is greater than the allowable
maximum of 8060.
The statement has been terminated.
What I recommend is storing any larger attributes in a separate table and
use relationships for data integrity.
Maybe you can show the code that represents "when I try to create one" and
the ACTUAL error message you receive, not your casual interpretation...
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189ae01c420b2$c7d24410$a601280a@.phx.gbl...
> This sql server is running our Microsoft CRM database. I
> am trying to create some custom attributes. When I try to
> create one it says that I am at the 8000 char row limit.
> I can not delete any attributes. Is there not a way
> around this? Thanks for your replys.|||I am not trying to manually create this table. The table
is created upon the installation of CRM and I am trying to
add an attribute to it within microsoft CRM. In CRM i get
the following error:
An error occurred during the addition of the new field.
The addition failed. For more information, see the event
log.
Event log error:
1.
dmLog: Failed to add new Picklist attribute (CFPcatagory)
to Account entity.
2.
dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
bytes.
I dont know if you are familiar with CRM deployment
manager, there is a section to create mappings, which
might be the same as the relationships as your talking
about. It will not let me modify any existing attribute,
even the ones that I have created. I cant delete an
attribute either.
Thanks again for your help.
>--Original Message--
>The error message is just a warning. You can go ahead
and create a table
>that is wider, just don't expect to use it all. For
example:
>CREATE TABLE dbo.blat
>(
> bar1 VARCHAR(5000),
> bar2 VARCHAR(5000)
>)
>GO
>Warning: The table 'blat' has been created but its
maximum row size (10025)
>exceeds the maximum number of bytes per row (8060).
INSERT or UPDATE of a
>row in this table will fail if the resulting row length
exceeds 8060 bytes.
>As the message states, the table was still created.
However, populating it
>with data will be more challenging. These work fine:
>INSERT blat SELECT 'a', 'b'
>INSERT blat SELECT REPLICATE('a', 5000), 'b'
>INSERT blat SELECT 'a', REPLICATE('b', 5000)
>But when you try and send more than 8060 bytes, you will
have problems, e.g.
>INSERT blat SELECT
> REPLICATE('a', 5000), REPLICATE('b', 5000)
>You get:
>Server: Msg 511, Level 16, State 1, Line 1
>Cannot create a row of size 10013 which is greater than
the allowable
>maximum of 8060.
>The statement has been terminated.
>What I recommend is storing any larger attributes in a
separate table and
>use relationships for data integrity.
>Maybe you can show the code that represents "when I try
to create one" and
>the ACTUAL error message you receive, not your casual
interpretation...
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"billy dodson" <billy@.pmicromart.com> wrote in message
>news:189ae01c420b2$c7d24410$a601280a@.phx.gbl...
>> This sql server is running our Microsoft CRM database.
I
>> am trying to create some custom attributes. When I try
to
>> create one it says that I am at the 8000 char row limit.
>> I can not delete any attributes. Is there not a way
>> around this? Thanks for your replys.
>
>.
>|||This limitation will be removed in Yukon. You will be able to do the
following (for example):
create table t1 (c1 varchar (5000), c2 varchar (5000))
go
insert into t1 values (replicate ('a', 5000), replicate ('b', 5000))
go
with no problems.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx.gbl...
> Is there any way around the 8000 byte limit?
> >--Original Message--
> >The actual row limit is 8060, and the max char/varchar
> column size is 8000
> >bytes.
> >"Billy Dodson" <billy@.pmicromart.com> wrote in message
> >news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> >> is the 8000 char row limit only an issue in standard
> >> edition? If I upgrade to enterprise edition will I not
> >> have this problem? Thanks.
> >
> >
> >.
> >|||Billy,
As stated, it is only a warning. How much of the 8060 char limit is being
used by the unmodified table?
If you have 16 bytes left, you can assign the new attribute to a text or
ntext column, and that will fit. Of course, you then have to deal with the
issues that arise from using text columns.
You can create an attribute table of nothing more than an identity or guid
column and the attribute and then just store the identity (4 bytes) or
rowguid (16 bytes) in your table.
You might also run statistics on the actual size of data being stored vs the
field size for all fields in the table. Knowing this will give you an idea
of how much space you can "safely" assign to the new attribute. The caveat
here is that you will have to check the length of everything on inserts and
updates.
Regards,
John
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx.gbl...
> Is there any way around the 8000 byte limit?
> >--Original Message--
> >The actual row limit is 8060, and the max char/varchar
> column size is 8000
> >bytes.
> >"Billy Dodson" <billy@.pmicromart.com> wrote in message
> >news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> >> is the 8000 char row limit only an issue in standard
> >> edition? If I upgrade to enterprise edition will I not
> >> have this problem? Thanks.
> >
> >
> >.
> >|||sounds like one for the CRM group if there is one - being unable to remove
user-defined attributes sounds like a design flaw
--
Niall Litchfield
Oracle DBA
Audit Commission UK
http://www.niall.litchfield.dial.pipex.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:1bad601c420b8$297548c0$a101280a@.phx.gbl...
> I am not trying to manually create this table. The table
> is created upon the installation of CRM and I am trying to
> add an attribute to it within microsoft CRM. In CRM i get
> the following error:
> An error occurred during the addition of the new field.
> The addition failed. For more information, see the event
> log.
> Event log error:
> 1.
> dmLog: Failed to add new Picklist attribute (CFPcatagory)
> to Account entity.
> 2.
> dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
> B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
> bytes.
>
> I dont know if you are familiar with CRM deployment
> manager, there is a section to create mappings, which
> might be the same as the relationships as your talking
> about. It will not let me modify any existing attribute,
> even the ones that I have created. I cant delete an
> attribute either.
> Thanks again for your help.
>
> >--Original Message--
> >The error message is just a warning. You can go ahead
> and create a table
> >that is wider, just don't expect to use it all. For
> example:
> >
> >CREATE TABLE dbo.blat
> >(
> > bar1 VARCHAR(5000),
> > bar2 VARCHAR(5000)
> >)
> >GO
> >
> >Warning: The table 'blat' has been created but its
> maximum row size (10025)
> >exceeds the maximum number of bytes per row (8060).
> INSERT or UPDATE of a
> >row in this table will fail if the resulting row length
> exceeds 8060 bytes.
> >
> >As the message states, the table was still created.
> However, populating it
> >with data will be more challenging. These work fine:
> >
> >INSERT blat SELECT 'a', 'b'
> >INSERT blat SELECT REPLICATE('a', 5000), 'b'
> >INSERT blat SELECT 'a', REPLICATE('b', 5000)
> >
> >But when you try and send more than 8060 bytes, you will
> have problems, e.g.
> >
> >INSERT blat SELECT
> > REPLICATE('a', 5000), REPLICATE('b', 5000)
> >
> >You get:
> >
> >Server: Msg 511, Level 16, State 1, Line 1
> >Cannot create a row of size 10013 which is greater than
> the allowable
> >maximum of 8060.
> >The statement has been terminated.
> >
> >What I recommend is storing any larger attributes in a
> separate table and
> >use relationships for data integrity.
> >
> >Maybe you can show the code that represents "when I try
> to create one" and
> >the ACTUAL error message you receive, not your casual
> interpretation...
> >
> >--
> >Aaron Bertrand
> >SQL Server MVP
> >http://www.aspfaq.com/
> >
> >
> >
> >
> >"billy dodson" <billy@.pmicromart.com> wrote in message
> >news:189ae01c420b2$c7d24410$a601280a@.phx.gbl...
> >> This sql server is running our Microsoft CRM database.
> I
> >> am trying to create some custom attributes. When I try
> to
> >> create one it says that I am at the 8000 char row limit.
> >> I can not delete any attributes. Is there not a way
> >> around this? Thanks for your replys.
> >
> >
> >.
> >

8000 char Row limit

is the 8000 char row limit only an issue in standard
edition? If I upgrade to enterprise edition will I not
have this problem? Thanks.It has nothing to do with the edition; it is a storage / engine limitation.
What exactly are you trying to do? Are you aware of the reasons for the
limit?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx
.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.|||The actual row limit is 8060, and the max char/varchar column size is 8000
bytes.
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx
.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.|||This sql server is running our Microsoft CRM database. I
am trying to create some custom attributes. When I try to
create one it says that I am at the 8000 char row limit.
I can not delete any attributes. Is there not a way
around this? Thanks for your replys.

>--Original Message--
>It has nothing to do with the edition; it is a storage /
engine limitation.
>What exactly are you trying to do? Are you aware of the
reasons for the
>limit?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
> news:1b64b01c420a7$4331a210$a301280a@.phx
.gbl...
>
>.
>|||Is there any way around the 8000 byte limit?

>--Original Message--
>The actual row limit is 8060, and the max char/varchar
column size is 8000
>bytes.
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
> news:1b64b01c420a7$4331a210$a301280a@.phx
.gbl...
>
>.
>|||The error message is just a warning. You can go ahead and create a table
that is wider, just don't expect to use it all. For example:
CREATE TABLE dbo.blat
(
bar1 VARCHAR(5000),
bar2 VARCHAR(5000)
)
GO
Warning: The table 'blat' has been created but its maximum row size (10025)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a
row in this table will fail if the resulting row length exceeds 8060 bytes.
As the message states, the table was still created. However, populating it
with data will be more challenging. These work fine:
INSERT blat SELECT 'a', 'b'
INSERT blat SELECT REPLICATE('a', 5000), 'b'
INSERT blat SELECT 'a', REPLICATE('b', 5000)
But when you try and send more than 8060 bytes, you will have problems, e.g.
INSERT blat SELECT
REPLICATE('a', 5000), REPLICATE('b', 5000)
You get:
Server: Msg 511, Level 16, State 1, Line 1
Cannot create a row of size 10013 which is greater than the allowable
maximum of 8060.
The statement has been terminated.
What I recommend is storing any larger attributes in a separate table and
use relationships for data integrity.
Maybe you can show the code that represents "when I try to create one" and
the ACTUAL error message you receive, not your casual interpretation...
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189ae01c420b2$c7d24410$a601280a@.phx
.gbl...
> This sql server is running our Microsoft CRM database. I
> am trying to create some custom attributes. When I try to
> create one it says that I am at the 8000 char row limit.
> I can not delete any attributes. Is there not a way
> around this? Thanks for your replys.|||I am not trying to manually create this table. The table
is created upon the installation of CRM and I am trying to
add an attribute to it within microsoft CRM. In CRM i get
the following error:
An error occurred during the addition of the new field.
The addition failed. For more information, see the event
log.
Event log error:
1.
dmLog: Failed to add new Picklist attribute (CFPcatagory)
to Account entity.
2.
dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
bytes.
I dont know if you are familiar with CRM deployment
manager, there is a section to create mappings, which
might be the same as the relationships as your talking
about. It will not let me modify any existing attribute,
even the ones that I have created. I cant delete an
attribute either.
Thanks again for your help.

>--Original Message--
>The error message is just a warning. You can go ahead
and create a table
>that is wider, just don't expect to use it all. For
example:
>CREATE TABLE dbo.blat
>(
> bar1 VARCHAR(5000),
> bar2 VARCHAR(5000)
> )
>GO
>Warning: The table 'blat' has been created but its
maximum row size (10025)
>exceeds the maximum number of bytes per row (8060).
INSERT or UPDATE of a
>row in this table will fail if the resulting row length
exceeds 8060 bytes.
>As the message states, the table was still created.
However, populating it
>with data will be more challenging. These work fine:
>INSERT blat SELECT 'a', 'b'
>INSERT blat SELECT REPLICATE('a', 5000), 'b'
>INSERT blat SELECT 'a', REPLICATE('b', 5000)
>But when you try and send more than 8060 bytes, you will
have problems, e.g.
>INSERT blat SELECT
> REPLICATE('a', 5000), REPLICATE('b', 5000)
>You get:
>Server: Msg 511, Level 16, State 1, Line 1
>Cannot create a row of size 10013 which is greater than
the allowable
>maximum of 8060.
>The statement has been terminated.
>What I recommend is storing any larger attributes in a
separate table and
>use relationships for data integrity.
>Maybe you can show the code that represents "when I try
to create one" and
>the ACTUAL error message you receive, not your casual
interpretation...
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"billy dodson" <billy@.pmicromart.com> wrote in message
> news:189ae01c420b2$c7d24410$a601280a@.phx
.gbl...
I
to
>
>.
>|||This limitation will be removed in Yukon. You will be able to do the
following (for example):
create table t1 (c1 varchar (5000), c2 varchar (5000))
go
insert into t1 values (replicate ('a', 5000), replicate ('b', 5000))
go
with no problems.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx
.gbl...
> Is there any way around the 8000 byte limit?
>
> column size is 8000|||Billy,
As stated, it is only a warning. How much of the 8060 char limit is being
used by the unmodified table?
If you have 16 bytes left, you can assign the new attribute to a text or
ntext column, and that will fit. Of course, you then have to deal with the
issues that arise from using text columns.
You can create an attribute table of nothing more than an identity or guid
column and the attribute and then just store the identity (4 bytes) or
rowguid (16 bytes) in your table.
You might also run statistics on the actual size of data being stored vs the
field size for all fields in the table. Knowing this will give you an idea
of how much space you can "safely" assign to the new attribute. The caveat
here is that you will have to check the length of everything on inserts and
updates.
Regards,
John
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx
.gbl...
> Is there any way around the 8000 byte limit?
>
> column size is 8000|||sounds like one for the CRM group if there is one - being unable to remove
user-defined attributes sounds like a design flaw
Niall Litchfield
Oracle DBA
Audit Commission UK
http://www.niall.litchfield.dial.pipex.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:1bad601c420b8$297548c0$a101280a@.phx
.gbl...
> I am not trying to manually create this table. The table
> is created upon the installation of CRM and I am trying to
> add an attribute to it within microsoft CRM. In CRM i get
> the following error:
> An error occurred during the addition of the new field.
> The addition failed. For more information, see the event
> log.
> Event log error:
> 1.
> dmLog: Failed to add new Picklist attribute (CFPcatagory)
> to Account entity.
> 2.
> dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
> B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
> bytes.
>
> I dont know if you are familiar with CRM deployment
> manager, there is a section to create mappings, which
> might be the same as the relationships as your talking
> about. It will not let me modify any existing attribute,
> even the ones that I have created. I cant delete an
> attribute either.
> Thanks again for your help.
>
> and create a table
> example:
> maximum row size (10025)
> INSERT or UPDATE of a
> exceeds 8060 bytes.
> However, populating it
> have problems, e.g.
> the allowable
> separate table and
> to create one" and
> interpretation...
> I
> to

Thursday, March 8, 2012

7.0 to 2000 Upgrade

Is this a reasonable way to upgrade a 7.0 server to 2000?
1. Backup the databases.
2. Move the database mdf and ldf files to a neutral
location on the server's drive.
3. Upgrade the server to Win 2k and Sql Server 2000.
4. Add pertinent logins.
5. Reattach the mdf and ldf files and let sql server
upgrade the databases "on the fly".
The reason I'm asking is that I've always been ultra-safe
in times past and used the copy wizard to copy my 7.0
databases to a 2000 server first.
Is an attach/reattach considered a supported way of doing
a 7.0 to 2000 conversion?
I'm a little scared of course because if it doesn't attach
for some reason, then I can try the .BAK files and if that
doesn't work, I'm dead.It is hard to find documentation that provides it one way or another.
However, iny my experience of doing it Attach/reattaching works fine. Just
make sure you have a backup copy of your databases becauase you'll not be
able to reattach them to a SQL 7.0 server after attaching them to SQL 2000.
The only concerns I can think of have to do more with the sort order, which
would show up when people start to connect and use the system. SQL 2000
supports attaching databases with different sort orders, but some stored
procedures that create temp tables may have issues without having the
collation order specified for them. Only thorough testing will reveal a
problem like this.
My *safest method* is to use DTS to transfer the databases to another
server, then copy them back.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"CLM" <anonymous@.discussions.microsoft.com> wrote in message
news:121bf01c3f57c$ec04e740$a501280a@.phx
.gbl...
> Is this a reasonable way to upgrade a 7.0 server to 2000?
> 1. Backup the databases.
> 2. Move the database mdf and ldf files to a neutral
> location on the server's drive.
> 3. Upgrade the server to Win 2k and Sql Server 2000.
> 4. Add pertinent logins.
> 5. Reattach the mdf and ldf files and let sql server
> upgrade the databases "on the fly".
> The reason I'm asking is that I've always been ultra-safe
> in times past and used the copy wizard to copy my 7.0
> databases to a 2000 server first.
> Is an attach/reattach considered a supported way of doing
> a 7.0 to 2000 conversion?
> I'm a little scared of course because if it doesn't attach
> for some reason, then I can try the .BAK files and if that
> doesn't work, I'm dead.
>

7.0 to 2000 Upgrade

Is this a reasonable way to upgrade a 7.0 server to 2000?
1. Backup the databases.
2. Move the database mdf and ldf files to a neutral
location on the server's drive.
3. Upgrade the server to Win 2k and Sql Server 2000.
4. Add pertinent logins.
5. Reattach the mdf and ldf files and let sql server
upgrade the databases "on the fly".
The reason I'm asking is that I've always been ultra-safe
in times past and used the copy wizard to copy my 7.0
databases to a 2000 server first.
Is an attach/reattach considered a supported way of doing
a 7.0 to 2000 conversion?
I'm a little scared of course because if it doesn't attach
for some reason, then I can try the .BAK files and if that
doesn't work, I'm dead.It is hard to find documentation that provides it one way or another.
However, iny my experience of doing it Attach/reattaching works fine. Just
make sure you have a backup copy of your databases becauase you'll not be
able to reattach them to a SQL 7.0 server after attaching them to SQL 2000.
The only concerns I can think of have to do more with the sort order, which
would show up when people start to connect and use the system. SQL 2000
supports attaching databases with different sort orders, but some stored
procedures that create temp tables may have issues without having the
collation order specified for them. Only thorough testing will reveal a
problem like this.
My *safest method* is to use DTS to transfer the databases to another
server, then copy them back.
--
*******************************************************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
*******************************************************************
"CLM" <anonymous@.discussions.microsoft.com> wrote in message
news:121bf01c3f57c$ec04e740$a501280a@.phx.gbl...
> Is this a reasonable way to upgrade a 7.0 server to 2000?
> 1. Backup the databases.
> 2. Move the database mdf and ldf files to a neutral
> location on the server's drive.
> 3. Upgrade the server to Win 2k and Sql Server 2000.
> 4. Add pertinent logins.
> 5. Reattach the mdf and ldf files and let sql server
> upgrade the databases "on the fly".
> The reason I'm asking is that I've always been ultra-safe
> in times past and used the copy wizard to copy my 7.0
> databases to a 2000 server first.
> Is an attach/reattach considered a supported way of doing
> a 7.0 to 2000 conversion?
> I'm a little scared of course because if it doesn't attach
> for some reason, then I can try the .BAK files and if that
> doesn't work, I'm dead.
>|||If you are going to upgrade Windows, I'd recommend
reinstalling everything from scratch. Our experience with
Windows upgrading in place is that it works successfully
30% of the time or less. And if it fails, it can fail
really hard (blue screen on a system that will never boot
again, i.e., total data loss).
SQL Server upgrades (without upgrading the OS) usually
work. One thing you *MUST* do, however, is install the
latest MDAC prior to beginning the SQL Server upgrade.
If you are worried about the integrity of the databases or
their backups, be sure to do a DBCC CHECKDB on all your
databases before you start this. Fix any problems before
taking your backups or detaching.
Also, keep records of all the logical *and* physical file
names (including the disk drive letters/file paths) for
*every* database file! You might need to know these to
get a restore or attach to work. This information can be
recorded from your existing installation only as long as
the databases are still attached, so get it first.
Regarding one of your questions: Both the attach and
restore SQL operations will automatically convert a SQL 7
database to SQL 2000.
P.S. It isn't really necessary to detach the databases to
copy them. You can copy the files safely as long as SQL
Server is stopped.
--Scott
>--Original Message--
>Is this a reasonable way to upgrade a 7.0 server to 2000?
>1. Backup the databases.
>2. Move the database mdf and ldf files to a neutral
>location on the server's drive.
>3. Upgrade the server to Win 2k and Sql Server 2000.
>4. Add pertinent logins.
>5. Reattach the mdf and ldf files and let sql server
>upgrade the databases "on the fly".
>The reason I'm asking is that I've always been ultra-safe
>in times past and used the copy wizard to copy my 7.0
>databases to a 2000 server first.
>Is an attach/reattach considered a supported way of doing
>a 7.0 to 2000 conversion?
>I'm a little scared of course because if it doesn't
attach
>for some reason, then I can try the .BAK files and if
that
>doesn't work, I'm dead.
>.
>

Friday, February 24, 2012

64 bit Edition and 32bit Participate in VIRTUALSQL Cluster

Hi All

I have a requiment to update a SQL Cluster that I have, however we only have the budget to upgrade one of the servers participating in the Cluster.

Older servers are ML370 G4 Dual 3Ghz 10GB RAM - Windows 2003 Enterprise (existing)

the server I want to upgrade to is a

DL380 G5 Quad 3Ghz (Duo) - 20GB RAM - Windows 2003 Enterprise x64 edition (new)

I would also be upgrading to SQL 2005 Enterprise in the same upgrade (x64 edition on the new server)

What I want to know is if a x64bit Edition and a standard x86 edition both participate in the same VIRTUALSQL instance in a clustered environment?

Would appreciate assistance from any Microsoft people reading this post?

No,

All instances of SQL Server participating in a Cluster must be the same -either 32 bit or 64 bit.

However, you may want to consider running 32 bit SQL Server on the 64 bit Windows Server.

Or, you may forgo the Cluster, and using the 64 bit SQL Server as primary, create a Mirror server with the 32 bit server as a fail-over partner.

|||If you've got the cash for a SQL 2005 Enterprise license and a single DL380 don't skimp. Purchase another DL380, they aren't that expensive.

Sunday, February 19, 2012

6.5 upgrade to 2000

When using the upgrade wizard to upgrade from 6.5 to 2000 how do you get logons moved to the 2000 server. Do you need to select the master database to do this? Under what conditions should you select the master database?
thanks| When using the upgrade wizard to upgrade from 6.5 to 2000 how do you get
logons
| moved to the 2000 server. Do you need to select the master database to
do this?
| Under what conditions should you select the master database?
--
From SQL Server Books online:
In the System Configuration screen, in System objects to transfer, select
the object types to transfer from SQL Server 6.5 to SQL Server 2000:
Server configuration
Login and remote login registrations and server configuration options
relevant to SQL Server 2000 are transferred as part of the version upgrade.
Hope this helps,
--
Eric Cárdenas
SQL Server support

6.5 upgrade - pls help!

I am having problems upgrading from 6.5 to 2000 using the
upgrade wizard. We have a 6.5 server called medisec that
we want to upgrade to a 2000 server called medisec2000. I
wanted to test the upgrade so I made a copy of the 6.5
database from medisec server to another 6.5 server that I
called medisec2. I then ran the upgrade wizard from
medisec2 to medisec2000 which ran ok. I then wanted to
upgrade the 'live' medisec server so I deleted the
upgraded database and tried to run the upgrade wizard
again. I got an error "You have already started upgrading
from MEDISEC2. You can not consolidate MEDISEC into
MEDISEC2000. The export server name has been changed to
the server you already started to upgrade." It looks like
it doesn't like me trying to upgrade from a different sql
6.5 server as it thinks I am trying to consolidate from
multiple 6.5 servers. I am not doing this though and just
want to somehow 'reset' the test upgrade. I don't really
want to try reinstalling sql 2000 on medisec2000 as this
server is already running other live apps. Can I
somehow 'reset' the medisec2000 server so that I can run a
fresh upgrade from the other server'Nick,
Why not install another instance of SS2000 and upgrade to that instance.
Then detach the databases from your new instance and attach them to
MEDISEC2000.
After that, you can remove the temporary instance you used for your upgrade.
Russell Fields
"Nick Astles" <nick.astles@.coch.nhs.uk> wrote in message
news:116201c35b2e$65dd96f0$3501280a@.phx.gbl...
> I am having problems upgrading from 6.5 to 2000 using the
> upgrade wizard. We have a 6.5 server called medisec that
> we want to upgrade to a 2000 server called medisec2000. I
> wanted to test the upgrade so I made a copy of the 6.5
> database from medisec server to another 6.5 server that I
> called medisec2. I then ran the upgrade wizard from
> medisec2 to medisec2000 which ran ok. I then wanted to
> upgrade the 'live' medisec server so I deleted the
> upgraded database and tried to run the upgrade wizard
> again. I got an error "You have already started upgrading
> from MEDISEC2. You can not consolidate MEDISEC into
> MEDISEC2000. The export server name has been changed to
> the server you already started to upgrade." It looks like
> it doesn't like me trying to upgrade from a different sql
> 6.5 server as it thinks I am trying to consolidate from
> multiple 6.5 servers. I am not doing this though and just
> want to somehow 'reset' the test upgrade. I don't really
> want to try reinstalling sql 2000 on medisec2000 as this
> server is already running other live apps. Can I
> somehow 'reset' the medisec2000 server so that I can run a
> fresh upgrade from the other server'

6.5 Upgrade

Did as directed in article 818550 and still does not
work. Have two machines, one SS 6.5sp5a on Win 2k other
SS 2000 sp3 on Win 2k.
Now receiving in the application event viewer:
...
Error return from function CreateFile
in file CnvPipe.cpp
Line=143
rc=2
Msg=The system cannot find the file specified.
HELP.There is another article that describes a similar error:
http://support.microsoft.com/?id=246181.
Hope this helps.
--
Michiel Wories, SQL Server PM
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Lana Stokes" <lana.stokes@.aig.com> wrote in message
news:034101c3974c$829ad640$a401280a@.phx.gbl...
> Did as directed in article 818550 and still does not
> work. Have two machines, one SS 6.5sp5a on Win 2k other
> SS 2000 sp3 on Win 2k.
> Now receiving in the application event viewer:
> ...
> Error return from function CreateFile
> in file CnvPipe.cpp
> Line=143
> rc=2
> Msg=The system cannot find the file specified.
> HELP.
>

6.5 upgrade

I am having trouble upgrading from SQL 6.4 to SQL 2000
using the wizard.
The wizard runs nicely until I get to 'Export and Import
via Named pipes', then I get the following message:
Export.exe on the remote machine was hung...
Export Exit Code: 259 - export.exe -CodePage 1252 -
DeviceType Pipe -AllTables yes -MasterPath
C:\MSSQL\DATA\MASTER.DAT -DatabaseName Comp2 -DevicePath
\\.\pipe\~cnvpipe0
Import Exit Code: -1 - ~cnvpipe0
Msg 4854, Level 21, State 1, Server RLINKDEST, Procedure ,
Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]****
Time:10-14-2003 10:27:21.125
Error return from function CreateFile
in file CnvPipe.cpp
Line=143
rc=5
Msg=Access is denied.
I have the same SA password on all accounts, and I have
set all ODBC drivers to connect in the same way, via named
pipes.
Please help!
Thank you
SusanneIf this is a 2 machine upgrade, then the SQL Server startup account on the
SQL 6.5 box may not have permission to the SQL Server 2000 machine.
Rand
This posting is provided "as is" with no warranties and confers no rights.

6.5 to 6.5

I want to upgrade our 6.5 sql server to sql server 2000 but first I
want to create another 6.5 first. This way when I screw the pooch I
won't take down our only database.
Anyway I was planning on creating a new database and then restore it
with a dump from the original. If there is an easier way please let
me know.
I've been making daily backups via a CD burner of the folder MSSQL and
backing it up once a week with a dat drive. I"ve also started doing
the dumps each day also.
As you can probably tell I've very new to this.
We use the Platypus 3.0 database frontend by Boardtown.
Thanks for all the help you can give me.<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
Not sure whether dumps from 6.5 can be read but to me, it sounds better to
have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
with 6.5. Run the import database tool, which will copy all objects and data
to SQL 2000.|||Hi,
(You cant restore a SQL 6.5 server database to SQL 2000 server due to
architectural changes.)
The only way to upgrade SQL 6.5 database to SQL 2000 is using the "Upgrade
Wizard" coming with SQL 2000.
You can either perform the upgrade :-
1. In the network using Named pipes protocol
2. Install SQL 6.5 in new server and have the upgrade in the same server
Steps for 1.
1. Install SQL 2000 and SP3a
2. Install SQL 6.5 sp5a
3. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Steps for 2.
1. Install SQL 2000 and SP3a in New server
2. Install SQL 6.5 and SP5a ina new server (With the same folder structure
as existing server)
3. Stop SQL 6.5 server in both servers
4. Copy the physical DAT files (Data and log files) from Existing to new
server in the same folder including system databases
5. STArt SQL 6.5 in server, this will make the new SQL 6.5 server same as
existing
7. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Second step will be fast since the upgrade is happening in the same machine.
Incase if you are using the First step then ensure that network is up and
stable.
Thanks
Hari
MCDBA
<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
>
> I've been making daily backups via a CD burner of the folder MSSQL and
> backing it up once a week with a dat drive. I"ve also started doing
> the dumps each day also.
> As you can probably tell I've very new to this.
> We use the Platypus 3.0 database frontend by Boardtown.
>
> Thanks for all the help you can give me.|||On Sun, 16 May 2004 23:05:51 +0200, "Egbert Nierop \(MVP for IIS\)"
<egbert_nierop@.nospam.invalid> wrote:
><kg7poe@.sti.net> wrote in message
>news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
>> I want to upgrade our 6.5 sql server to sql server 2000 but first I
>> want to create another 6.5 first. This way when I screw the pooch I
>> won't take down our only database.
>> Anyway I was planning on creating a new database and then restore it
>> with a dump from the original. If there is an easier way please let
>> me know.
>Not sure whether dumps from 6.5 can be read but to me, it sounds better to
>have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
>with 6.5. Run the import database tool, which will copy all objects and data
>to SQL 2000.
>
Actually I want to resotre another 6.5 with a dump from the original.
Of course I can't even get the new one to work with the backup
database. I made sure its on the same hard drive letter and even
copied over the whole MSSQL folder but so far no luck.

6.5 to 6.5

I want to upgrade our 6.5 sql server to sql server 2000 but first I
want to create another 6.5 first. This way when I screw the pooch I
won't take down our only database.
Anyway I was planning on creating a new database and then restore it
with a dump from the original. If there is an easier way please let
me know.
I've been making daily backups via a CD burner of the folder MSSQL and
backing it up once a week with a dat drive. I"ve also started doing
the dumps each day also.
As you can probably tell I've very new to this.
We use the Platypus 3.0 database frontend by Boardtown.
Thanks for all the help you can give me.
<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
Not sure whether dumps from 6.5 can be read but to me, it sounds better to
have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
with 6.5. Run the import database tool, which will copy all objects and data
to SQL 2000.
|||Hi,
(You cant restore a SQL 6.5 server database to SQL 2000 server due to
architectural changes.)
The only way to upgrade SQL 6.5 database to SQL 2000 is using the "Upgrade
Wizard" coming with SQL 2000.
You can either perform the upgrade :-
1. In the network using Named pipes protocol
2. Install SQL 6.5 in new server and have the upgrade in the same server
Steps for 1.
1. Install SQL 2000 and SP3a
2. Install SQL 6.5 sp5a
3. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Steps for 2.
1. Install SQL 2000 and SP3a in New server
2. Install SQL 6.5 and SP5a ina new server (With the same folder structure
as existing server)
3. Stop SQL 6.5 server in both servers
4. Copy the physical DAT files (Data and log files) from Existing to new
server in the same folder including system databases
5. STArt SQL 6.5 in server, this will make the new SQL 6.5 server same as
existing
7. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Second step will be fast since the upgrade is happening in the same machine.
Incase if you are using the First step then ensure that network is up and
stable.
Thanks
Hari
MCDBA
<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
>
> I've been making daily backups via a CD burner of the folder MSSQL and
> backing it up once a week with a dat drive. I"ve also started doing
> the dumps each day also.
> As you can probably tell I've very new to this.
> We use the Platypus 3.0 database frontend by Boardtown.
>
> Thanks for all the help you can give me.
|||On Sun, 16 May 2004 23:05:51 +0200, "Egbert Nierop \(MVP for IIS\)"
<egbert_nierop@.nospam.invalid> wrote:

><kg7poe@.sti.net> wrote in message
>news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com.. .
>Not sure whether dumps from 6.5 can be read but to me, it sounds better to
>have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
>with 6.5. Run the import database tool, which will copy all objects and data
>to SQL 2000.
>
Actually I want to resotre another 6.5 with a dump from the original.
Of course I can't even get the new one to work with the backup
database. I made sure its on the same hard drive letter and even
copied over the whole MSSQL folder but so far no luck.

6.5 to 6.5

I want to upgrade our 6.5 sql server to sql server 2000 but first I
want to create another 6.5 first. This way when I screw the pooch I
won't take down our only database.
Anyway I was planning on creating a new database and then restore it
with a dump from the original. If there is an easier way please let
me know.
I've been making daily backups via a CD burner of the folder MSSQL and
backing it up once a week with a dat drive. I"ve also started doing
the dumps each day also.
As you can probably tell I've very new to this.
We use the Platypus 3.0 database frontend by Boardtown.
Thanks for all the help you can give me.<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.
4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
Not sure whether dumps from 6.5 can be read but to me, it sounds better to
have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
with 6.5. Run the import database tool, which will copy all objects and data
to SQL 2000.|||Hi,
(You cant restore a SQL 6.5 server database to SQL 2000 server due to
architectural changes.)
The only way to upgrade SQL 6.5 database to SQL 2000 is using the "Upgrade
Wizard" coming with SQL 2000.
You can either perform the upgrade :-
1. In the network using Named pipes protocol
2. Install SQL 6.5 in new server and have the upgrade in the same server
Steps for 1.
1. Install SQL 2000 and SP3a
2. Install SQL 6.5 sp5a
3. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Steps for 2.
1. Install SQL 2000 and SP3a in New server
2. Install SQL 6.5 and SP5a ina new server (With the same folder structure
as existing server)
3. Stop SQL 6.5 server in both servers
4. Copy the physical DAT files (Data and log files) from Existing to new
server in the same folder including system databases
5. STArt SQL 6.5 in server, this will make the new SQL 6.5 server same as
existing
7. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Second step will be fast since the upgrade is happening in the same machine.
Incase if you are using the First step then ensure that network is up and
stable.
Thanks
Hari
MCDBA
<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.
4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
>
> I've been making daily backups via a CD burner of the folder MSSQL and
> backing it up once a week with a dat drive. I"ve also started doing
> the dumps each day also.
> As you can probably tell I've very new to this.
> We use the Platypus 3.0 database frontend by Boardtown.
>
> Thanks for all the help you can give me.|||On Sun, 16 May 2004 23:05:51 +0200, "Egbert Nierop \(MVP for IIS\)"
<egbert_nierop@.nospam.invalid> wrote:

><kg7poe@.sti.net> wrote in message
> news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.
4ax.com...
>Not sure whether dumps from 6.5 can be read but to me, it sounds better to
>have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
>with 6.5. Run the import database tool, which will copy all objects and dat
a
>to SQL 2000.
>
Actually I want to resotre another 6.5 with a dump from the original.
Of course I can't even get the new one to work with the backup
database. I made sure its on the same hard drive letter and even
copied over the whole MSSQL folder but so far no luck.

6.5 to 2000 upgrade wizard

where is the name of the log file for the upgrade wizard?
thanksnevermind, found them.

6.5 to 2000 upgrade - Logon failure...

Hi All,
I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a new
server running Win2003Server and SQL 2000.
The Upgrade Wizard is dying on the Import and Export phase and giving the
error described in KB Article 302850. The cause being a mismatch of users
and permissions between the two machines and the users that are starting the
MSSQLSever service. I attempted to follow the steps listed in this article,
but ran in the problem that I cannot seem to add a domain user from the NT4
machine as a Local Admin on the 2003 Server (no Active directory support I
guess?)
Any other options for me to get this upgrade to happen?
Thanks.
- MaxinNJ
Hi
The solution in:
http://support.microsoft.com/default...b;en-us;818550
is to upgrade your OS on the NT server. You may want to find a third machine
to do this on! Alternatively you may want to try and use the Import
Wizard/DTS or BCP to retrieve the data (and possibly script the database to
get the DDL).
John
"MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
news:498B1C83-7395-4604-B6DE-D0CF35A53D9B@.microsoft.com...
> Hi All,
> I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a
> new
> server running Win2003Server and SQL 2000.
> The Upgrade Wizard is dying on the Import and Export phase and giving the
> error described in KB Article 302850. The cause being a mismatch of users
> and permissions between the two machines and the users that are starting
> the
> MSSQLSever service. I attempted to follow the steps listed in this
> article,
> but ran in the problem that I cannot seem to add a domain user from the
> NT4
> machine as a Local Admin on the 2003 Server (no Active directory support I
> guess?)
> Any other options for me to get this upgrade to happen?
> Thanks.
> - MaxinNJ
|||Thanks John - missed that KB article. Well, this at least explains things
Off to find a spare machine and dig up SQL 6.5 disks!
- Max
"John Bell" wrote:

> Hi
> The solution in:
> http://support.microsoft.com/default...b;en-us;818550
> is to upgrade your OS on the NT server. You may want to find a third machine
> to do this on! Alternatively you may want to try and use the Import
> Wizard/DTS or BCP to retrieve the data (and possibly script the database to
> get the DDL).
> John
> "MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
> news:498B1C83-7395-4604-B6DE-D0CF35A53D9B@.microsoft.com...
>
>
|||Hi
Make sure it is also service packed to the correct level.
John
"MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
news:DF507549-A9B1-40ED-BF65-0EB53DFB0DDC@.microsoft.com...[vbcol=seagreen]
> Thanks John - missed that KB article. Well, this at least explains things
>
> Off to find a spare machine and dig up SQL 6.5 disks!
> - Max
> "John Bell" wrote:

6.5 to 2000 upgrade - Logon failure...

Hi All,
I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a new
server running Win2003Server and SQL 2000.
The Upgrade Wizard is dying on the Import and Export phase and giving the
error described in KB Article 302850. The cause being a mismatch of users
and permissions between the two machines and the users that are starting the
MSSQLSever service. I attempted to follow the steps listed in this article,
but ran in the problem that I cannot seem to add a domain user from the NT4
machine as a Local Admin on the 2003 Server (no Active directory support I
guess?)
Any other options for me to get this upgrade to happen?
Thanks.
- MaxinNJHi
The solution in:
http://support.microsoft.com/defaul...kb;en-us;818550
is to upgrade your OS on the NT server. You may want to find a third machine
to do this on! Alternatively you may want to try and use the Import
Wizard/DTS or BCP to retrieve the data (and possibly script the database to
get the DDL).
John
"MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
news:498B1C83-7395-4604-B6DE-D0CF35A53D9B@.microsoft.com...
> Hi All,
> I am attempting to upgrade my SQL 6.5 databases running on NT4 SP6 to a
> new
> server running Win2003Server and SQL 2000.
> The Upgrade Wizard is dying on the Import and Export phase and giving the
> error described in KB Article 302850. The cause being a mismatch of users
> and permissions between the two machines and the users that are starting
> the
> MSSQLSever service. I attempted to follow the steps listed in this
> article,
> but ran in the problem that I cannot seem to add a domain user from the
> NT4
> machine as a Local Admin on the 2003 Server (no Active directory support I
> guess?)
> Any other options for me to get this upgrade to happen?
> Thanks.
> - MaxinNJ|||Thanks John - missed that KB article. Well, this at least explains things :
)
Off to find a spare machine and dig up SQL 6.5 disks!
- Max
"John Bell" wrote:

> Hi
> The solution in:
> http://support.microsoft.com/defaul...kb;en-us;818550
> is to upgrade your OS on the NT server. You may want to find a third machi
ne
> to do this on! Alternatively you may want to try and use the Import
> Wizard/DTS or BCP to retrieve the data (and possibly script the database t
o
> get the DDL).
> John
> "MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
> news:498B1C83-7395-4604-B6DE-D0CF35A53D9B@.microsoft.com...
>
>|||Hi
Make sure it is also service packed to the correct level.
John
"MaxinNJ" <MaxinNJ@.discussions.microsoft.com> wrote in message
news:DF507549-A9B1-40ED-BF65-0EB53DFB0DDC@.microsoft.com...[vbcol=seagreen]
> Thanks John - missed that KB article. Well, this at least explains things
>
> Off to find a spare machine and dig up SQL 6.5 disks!
> - Max
> "John Bell" wrote:
>