Hello all,
I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of system
memory. SQL never uses more than 2GB of system memory. What is the correct
configuration of the 3GB and PAE switches in the boot.ini file?
Roy Love
SupportOnline.BIZ
Roy,
From the SQL BOL:
To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
support a 3-GB virtual address space, you must add the /3gb parameter to the
boot.ini file. This allows user applications to address 3 GB of virtual
memory and reserves 1 GB of virtual memory for the operating system.
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> Hello all,
> I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> system
> memory. SQL never uses more than 2GB of system memory. What is the
> correct
> configuration of the 3GB and PAE switches in the boot.ini file?
> --
> Roy Love
> SupportOnline.BIZ
|||I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
setting AWE to the amount of memory in the server. You mentioned virtural
memory, I am talking about physical memory.
thanks,
Roy Love
SupportOnline.BIZ
"Jerry Spivey" wrote:
> Roy,
> From the SQL BOL:
> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
> support a 3-GB virtual address space, you must add the /3gb parameter to the
> boot.ini file. This allows user applications to address 3 GB of virtual
> memory and reserves 1 GB of virtual memory for the operating system.
> HTH
> Jerry
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>
>
|||Roy,
Might take a look at:
http://support.microsoft.com/default...274750&sd=tech
and
http://support.microsoft.com/kb/283037/
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...[vbcol=seagreen]
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
|||If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memory. I think that 2Gb is
for the buffer pool (data cache, cached plans etc), and MemToLeave area is outside of that. So,
*possibly* you could tweak out a bit more using PAE and AWE:
Today (roughly):
BP: 1.7 GB
MemToLeave: 0.3 GB
With AWE and PAE:
BP: 2 GB
MemToLeave 0.3 GB
Here's a good place to learn more about how SQL Server uses memory, AWE etc.:
http://blogs.msdn.com/slavao/
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...[vbcol=seagreen]
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
|||Is Windows seeing the full 4GB?
Some raid cards (hot swap pci etc) can "steal" some memory unless you use
/PAE.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23BPfWr70FHA.3376@.TK2MSFTNGP14.phx.gbl...
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB
> memory. I think that 2Gb is for the buffer pool (data cache, cached plans
> etc), and MemToLeave area is outside of that. So, *possibly* you could
> tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE
> etc.: http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>
|||Thanks Tibor,
I am running SQL2000 Enterprise Edition, not SE.
Regards,
Roy Love
SupportOnline.BIZ
"Tibor Karaszi" wrote:
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memory. I think that 2Gb is
> for the buffer pool (data cache, cached plans etc), and MemToLeave area is outside of that. So,
> *possibly* you could tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE etc.:
> http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>
|||Then you need either the /3GB switch or PAE and AWE. Aside, all memory in Windows is virtual memory,
An application doesn't address memory directly, it goes by the OS memory manager. Here's a start:
http://support.microsoft.com/default...b;en-us;274750
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:76402F72-A1B6-466F-802F-234A1033E0AE@.microsoft.com...[vbcol=seagreen]
> Thanks Tibor,
> I am running SQL2000 Enterprise Edition, not SE.
> Regards,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Tibor Karaszi" wrote:
Showing posts with label sql2000. Show all posts
Showing posts with label sql2000. Show all posts
Tuesday, March 27, 2012
Correct Memory Configuration for 4GB/W2K3 Enterprise
Hello all,
I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of system
memory. SQL never uses more than 2GB of system memory. What is the correct
configuration of the 3GB and PAE switches in the boot.ini file?
--
Roy Love
SupportOnline.BIZRoy,
From the SQL BOL:
To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
support a 3-GB virtual address space, you must add the /3gb parameter to the
boot.ini file. This allows user applications to address 3 GB of virtual
memory and reserves 1 GB of virtual memory for the operating system.
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> Hello all,
> I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> system
> memory. SQL never uses more than 2GB of system memory. What is the
> correct
> configuration of the 3GB and PAE switches in the boot.ini file?
> --
> Roy Love
> SupportOnline.BIZ|||I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
setting AWE to the amount of memory in the server. You mentioned virtural
memory, I am talking about physical memory.
thanks,
--
Roy Love
SupportOnline.BIZ
"Jerry Spivey" wrote:
> Roy,
> From the SQL BOL:
> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
> support a 3-GB virtual address space, you must add the /3gb parameter to the
> boot.ini file. This allows user applications to address 3 GB of virtual
> memory and reserves 1 GB of virtual memory for the operating system.
> HTH
> Jerry
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> > Hello all,
> >
> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> > system
> > memory. SQL never uses more than 2GB of system memory. What is the
> > correct
> > configuration of the 3GB and PAE switches in the boot.ini file?
> > --
> > Roy Love
> > SupportOnline.BIZ
>
>|||Roy,
Might take a look at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
and
http://support.microsoft.com/kb/283037/
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
>> Roy,
>> From the SQL BOL:
>> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server
>> to
>> support a 3-GB virtual address space, you must add the /3gb parameter to
>> the
>> boot.ini file. This allows user applications to address 3 GB of virtual
>> memory and reserves 1 GB of virtual memory for the operating system.
>> HTH
>> Jerry
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> > Hello all,
>> >
>> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> > system
>> > memory. SQL never uses more than 2GB of system memory. What is the
>> > correct
>> > configuration of the 3GB and PAE switches in the boot.ini file?
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>>|||If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memory. I think that 2Gb is
for the buffer pool (data cache, cached plans etc), and MemToLeave area is outside of that. So,
*possibly* you could tweak out a bit more using PAE and AWE:
Today (roughly):
BP: 1.7 GB
MemToLeave: 0.3 GB
With AWE and PAE:
BP: 2 GB
MemToLeave 0.3 GB
Here's a good place to learn more about how SQL Server uses memory, AWE etc.:
http://blogs.msdn.com/slavao/
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
>> Roy,
>> From the SQL BOL:
>> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
>> support a 3-GB virtual address space, you must add the /3gb parameter to the
>> boot.ini file. This allows user applications to address 3 GB of virtual
>> memory and reserves 1 GB of virtual memory for the operating system.
>> HTH
>> Jerry
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> > Hello all,
>> >
>> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> > system
>> > memory. SQL never uses more than 2GB of system memory. What is the
>> > correct
>> > configuration of the 3GB and PAE switches in the boot.ini file?
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>>|||Is Windows seeing the full 4GB?
Some raid cards (hot swap pci etc) can "steal" some memory unless you use
/PAE.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23BPfWr70FHA.3376@.TK2MSFTNGP14.phx.gbl...
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB
> memory. I think that 2Gb is for the buffer pool (data cache, cached plans
> etc), and MemToLeave area is outside of that. So, *possibly* you could
> tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE
> etc.: http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
>> setting AWE to the amount of memory in the server. You mentioned
>> virtural
>> memory, I am talking about physical memory.
>> thanks,
>> --
>> Roy Love
>> SupportOnline.BIZ
>>
>> "Jerry Spivey" wrote:
>> Roy,
>> From the SQL BOL:
>> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter
>> Server to
>> support a 3-GB virtual address space, you must add the /3gb parameter to
>> the
>> boot.ini file. This allows user applications to address 3 GB of virtual
>> memory and reserves 1 GB of virtual memory for the operating system.
>> HTH
>> Jerry
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> > Hello all,
>> >
>> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> > system
>> > memory. SQL never uses more than 2GB of system memory. What is the
>> > correct
>> > configuration of the 3GB and PAE switches in the boot.ini file?
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>>
>|||Thanks Tibor,
I am running SQL2000 Enterprise Edition, not SE.
Regards,
--
Roy Love
SupportOnline.BIZ
"Tibor Karaszi" wrote:
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memory. I think that 2Gb is
> for the buffer pool (data cache, cached plans etc), and MemToLeave area is outside of that. So,
> *possibly* you could tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE etc.:
> http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
> >I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> > setting AWE to the amount of memory in the server. You mentioned virtural
> > memory, I am talking about physical memory.
> >
> > thanks,
> > --
> > Roy Love
> > SupportOnline.BIZ
> >
> >
> > "Jerry Spivey" wrote:
> >
> >> Roy,
> >>
> >> From the SQL BOL:
> >>
> >> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
> >> support a 3-GB virtual address space, you must add the /3gb parameter to the
> >> boot.ini file. This allows user applications to address 3 GB of virtual
> >> memory and reserves 1 GB of virtual memory for the operating system.
> >>
> >> HTH
> >>
> >> Jerry
> >> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> >> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> >> > Hello all,
> >> >
> >> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> >> > system
> >> > memory. SQL never uses more than 2GB of system memory. What is the
> >> > correct
> >> > configuration of the 3GB and PAE switches in the boot.ini file?
> >> > --
> >> > Roy Love
> >> > SupportOnline.BIZ
> >>
> >>
> >>
>|||Then you need either the /3GB switch or PAE and AWE. Aside, all memory in Windows is virtual memory,
An application doesn't address memory directly, it goes by the OS memory manager. Here's a start:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:76402F72-A1B6-466F-802F-234A1033E0AE@.microsoft.com...
> Thanks Tibor,
> I am running SQL2000 Enterprise Edition, not SE.
> Regards,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Tibor Karaszi" wrote:
>> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memory. I think that 2Gb
>> is
>> for the buffer pool (data cache, cached plans etc), and MemToLeave area is outside of that. So,
>> *possibly* you could tweak out a bit more using PAE and AWE:
>> Today (roughly):
>> BP: 1.7 GB
>> MemToLeave: 0.3 GB
>> With AWE and PAE:
>> BP: 2 GB
>> MemToLeave 0.3 GB
>> Here's a good place to learn more about how SQL Server uses memory, AWE etc.:
>> http://blogs.msdn.com/slavao/
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>> >I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
>> > setting AWE to the amount of memory in the server. You mentioned virtural
>> > memory, I am talking about physical memory.
>> >
>> > thanks,
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>> >
>> >
>> > "Jerry Spivey" wrote:
>> >
>> >> Roy,
>> >>
>> >> From the SQL BOL:
>> >>
>> >> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
>> >> support a 3-GB virtual address space, you must add the /3gb parameter to the
>> >> boot.ini file. This allows user applications to address 3 GB of virtual
>> >> memory and reserves 1 GB of virtual memory for the operating system.
>> >>
>> >> HTH
>> >>
>> >> Jerry
>> >> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> >> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> >> > Hello all,
>> >> >
>> >> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> >> > system
>> >> > memory. SQL never uses more than 2GB of system memory. What is the
>> >> > correct
>> >> > configuration of the 3GB and PAE switches in the boot.ini file?
>> >> > --
>> >> > Roy Love
>> >> > SupportOnline.BIZ
>> >>
>> >>
>> >>
>>
I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of system
memory. SQL never uses more than 2GB of system memory. What is the correct
configuration of the 3GB and PAE switches in the boot.ini file?
--
Roy Love
SupportOnline.BIZRoy,
From the SQL BOL:
To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
support a 3-GB virtual address space, you must add the /3gb parameter to the
boot.ini file. This allows user applications to address 3 GB of virtual
memory and reserves 1 GB of virtual memory for the operating system.
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> Hello all,
> I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> system
> memory. SQL never uses more than 2GB of system memory. What is the
> correct
> configuration of the 3GB and PAE switches in the boot.ini file?
> --
> Roy Love
> SupportOnline.BIZ|||I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
setting AWE to the amount of memory in the server. You mentioned virtural
memory, I am talking about physical memory.
thanks,
--
Roy Love
SupportOnline.BIZ
"Jerry Spivey" wrote:
> Roy,
> From the SQL BOL:
> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
> support a 3-GB virtual address space, you must add the /3gb parameter to the
> boot.ini file. This allows user applications to address 3 GB of virtual
> memory and reserves 1 GB of virtual memory for the operating system.
> HTH
> Jerry
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> > Hello all,
> >
> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> > system
> > memory. SQL never uses more than 2GB of system memory. What is the
> > correct
> > configuration of the 3GB and PAE switches in the boot.ini file?
> > --
> > Roy Love
> > SupportOnline.BIZ
>
>|||Roy,
Might take a look at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
and
http://support.microsoft.com/kb/283037/
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
>> Roy,
>> From the SQL BOL:
>> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server
>> to
>> support a 3-GB virtual address space, you must add the /3gb parameter to
>> the
>> boot.ini file. This allows user applications to address 3 GB of virtual
>> memory and reserves 1 GB of virtual memory for the operating system.
>> HTH
>> Jerry
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> > Hello all,
>> >
>> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> > system
>> > memory. SQL never uses more than 2GB of system memory. What is the
>> > correct
>> > configuration of the 3GB and PAE switches in the boot.ini file?
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>>|||If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memory. I think that 2Gb is
for the buffer pool (data cache, cached plans etc), and MemToLeave area is outside of that. So,
*possibly* you could tweak out a bit more using PAE and AWE:
Today (roughly):
BP: 1.7 GB
MemToLeave: 0.3 GB
With AWE and PAE:
BP: 2 GB
MemToLeave 0.3 GB
Here's a good place to learn more about how SQL Server uses memory, AWE etc.:
http://blogs.msdn.com/slavao/
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
>> Roy,
>> From the SQL BOL:
>> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
>> support a 3-GB virtual address space, you must add the /3gb parameter to the
>> boot.ini file. This allows user applications to address 3 GB of virtual
>> memory and reserves 1 GB of virtual memory for the operating system.
>> HTH
>> Jerry
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> > Hello all,
>> >
>> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> > system
>> > memory. SQL never uses more than 2GB of system memory. What is the
>> > correct
>> > configuration of the 3GB and PAE switches in the boot.ini file?
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>>|||Is Windows seeing the full 4GB?
Some raid cards (hot swap pci etc) can "steal" some memory unless you use
/PAE.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23BPfWr70FHA.3376@.TK2MSFTNGP14.phx.gbl...
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB
> memory. I think that 2Gb is for the buffer pool (data cache, cached plans
> etc), and MemToLeave area is outside of that. So, *possibly* you could
> tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE
> etc.: http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
>> setting AWE to the amount of memory in the server. You mentioned
>> virtural
>> memory, I am talking about physical memory.
>> thanks,
>> --
>> Roy Love
>> SupportOnline.BIZ
>>
>> "Jerry Spivey" wrote:
>> Roy,
>> From the SQL BOL:
>> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter
>> Server to
>> support a 3-GB virtual address space, you must add the /3gb parameter to
>> the
>> boot.ini file. This allows user applications to address 3 GB of virtual
>> memory and reserves 1 GB of virtual memory for the operating system.
>> HTH
>> Jerry
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> > Hello all,
>> >
>> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> > system
>> > memory. SQL never uses more than 2GB of system memory. What is the
>> > correct
>> > configuration of the 3GB and PAE switches in the boot.ini file?
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>>
>|||Thanks Tibor,
I am running SQL2000 Enterprise Edition, not SE.
Regards,
--
Roy Love
SupportOnline.BIZ
"Tibor Karaszi" wrote:
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memory. I think that 2Gb is
> for the buffer pool (data cache, cached plans etc), and MemToLeave area is outside of that. So,
> *possibly* you could tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE etc.:
> http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
> >I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> > setting AWE to the amount of memory in the server. You mentioned virtural
> > memory, I am talking about physical memory.
> >
> > thanks,
> > --
> > Roy Love
> > SupportOnline.BIZ
> >
> >
> > "Jerry Spivey" wrote:
> >
> >> Roy,
> >>
> >> From the SQL BOL:
> >>
> >> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
> >> support a 3-GB virtual address space, you must add the /3gb parameter to the
> >> boot.ini file. This allows user applications to address 3 GB of virtual
> >> memory and reserves 1 GB of virtual memory for the operating system.
> >>
> >> HTH
> >>
> >> Jerry
> >> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> >> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> >> > Hello all,
> >> >
> >> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> >> > system
> >> > memory. SQL never uses more than 2GB of system memory. What is the
> >> > correct
> >> > configuration of the 3GB and PAE switches in the boot.ini file?
> >> > --
> >> > Roy Love
> >> > SupportOnline.BIZ
> >>
> >>
> >>
>|||Then you need either the /3GB switch or PAE and AWE. Aside, all memory in Windows is virtual memory,
An application doesn't address memory directly, it goes by the OS memory manager. Here's a start:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:76402F72-A1B6-466F-802F-234A1033E0AE@.microsoft.com...
> Thanks Tibor,
> I am running SQL2000 Enterprise Edition, not SE.
> Regards,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Tibor Karaszi" wrote:
>> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memory. I think that 2Gb
>> is
>> for the buffer pool (data cache, cached plans etc), and MemToLeave area is outside of that. So,
>> *possibly* you could tweak out a bit more using PAE and AWE:
>> Today (roughly):
>> BP: 1.7 GB
>> MemToLeave: 0.3 GB
>> With AWE and PAE:
>> BP: 2 GB
>> MemToLeave 0.3 GB
>> Here's a good place to learn more about how SQL Server uses memory, AWE etc.:
>> http://blogs.msdn.com/slavao/
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>> >I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
>> > setting AWE to the amount of memory in the server. You mentioned virtural
>> > memory, I am talking about physical memory.
>> >
>> > thanks,
>> > --
>> > Roy Love
>> > SupportOnline.BIZ
>> >
>> >
>> > "Jerry Spivey" wrote:
>> >
>> >> Roy,
>> >>
>> >> From the SQL BOL:
>> >>
>> >> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
>> >> support a 3-GB virtual address space, you must add the /3gb parameter to the
>> >> boot.ini file. This allows user applications to address 3 GB of virtual
>> >> memory and reserves 1 GB of virtual memory for the operating system.
>> >>
>> >> HTH
>> >>
>> >> Jerry
>> >> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
>> >> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>> >> > Hello all,
>> >> >
>> >> > I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
>> >> > system
>> >> > memory. SQL never uses more than 2GB of system memory. What is the
>> >> > correct
>> >> > configuration of the 3GB and PAE switches in the boot.ini file?
>> >> > --
>> >> > Roy Love
>> >> > SupportOnline.BIZ
>> >>
>> >>
>> >>
>>
Correct Memory Configuration for 4GB/W2K3 Enterprise
Hello all,
I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of system
memory. SQL never uses more than 2GB of system memory. What is the correct
configuration of the 3GB and PAE switches in the boot.ini file?
--
Roy Love
SupportOnline.BIZRoy,
From the SQL BOL:
To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
support a 3-GB virtual address space, you must add the /3gb parameter to the
boot.ini file. This allows user applications to address 3 GB of virtual
memory and reserves 1 GB of virtual memory for the operating system.
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> Hello all,
> I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> system
> memory. SQL never uses more than 2GB of system memory. What is the
> correct
> configuration of the 3GB and PAE switches in the boot.ini file?
> --
> Roy Love
> SupportOnline.BIZ|||I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
setting AWE to the amount of memory in the server. You mentioned virtural
memory, I am talking about physical memory.
thanks,
--
Roy Love
SupportOnline.BIZ
"Jerry Spivey" wrote:
> Roy,
> From the SQL BOL:
> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server
to
> support a 3-GB virtual address space, you must add the /3gb parameter to t
he
> boot.ini file. This allows user applications to address 3 GB of virtual
> memory and reserves 1 GB of virtual memory for the operating system.
> HTH
> Jerry
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>
>|||Roy,
Might take a look at:
http://support.microsoft.com/defaul...;274750&sd=tech
and
http://support.microsoft.com/kb/283037/
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...[vbcol=seagreen]
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
>|||If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memo
ry. I think that 2Gb is
for the buffer pool (data cache, cached plans etc), and MemToLeave area is o
utside of that. So,
*possibly* you could tweak out a bit more using PAE and AWE:
Today (roughly):
BP: 1.7 GB
MemToLeave: 0.3 GB
With AWE and PAE:
BP: 2 GB
MemToLeave 0.3 GB
Here's a good place to learn more about how SQL Server uses memory, AWE etc.
:
http://blogs.msdn.com/slavao/
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...[vbcol=seagreen]
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
>|||Is Windows seeing the full 4GB?
Some raid cards (hot swap pci etc) can "steal" some memory unless you use
/PAE.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23BPfWr70FHA.3376@.TK2MSFTNGP14.phx.gbl...
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB
> memory. I think that 2Gb is for the buffer pool (data cache, cached plans
> etc), and MemToLeave area is outside of that. So, *possibly* you could
> tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE
> etc.: http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>|||Thanks Tibor,
I am running SQL2000 Enterprise Edition, not SE.
Regards,
--
Roy Love
SupportOnline.BIZ
"Tibor Karaszi" wrote:
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB me
mory. I think that 2Gb is
> for the buffer pool (data cache, cached plans etc), and MemToLeave area is
outside of that. So,
> *possibly* you could tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE et
c.:
> http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>|||Then you need either the /3GB switch or PAE and AWE. Aside, all memory in Wi
ndows is virtual memory,
An application doesn't address memory directly, it goes by the OS memory man
ager. Here's a start:
http://support.microsoft.com/defaul...kb;en-us;274750
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:76402F72-A1B6-466F-802F-234A1033E0AE@.microsoft.com...[vbcol=seagreen]
> Thanks Tibor,
> I am running SQL2000 Enterprise Edition, not SE.
> Regards,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Tibor Karaszi" wrote:
>
I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of system
memory. SQL never uses more than 2GB of system memory. What is the correct
configuration of the 3GB and PAE switches in the boot.ini file?
--
Roy Love
SupportOnline.BIZRoy,
From the SQL BOL:
To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server to
support a 3-GB virtual address space, you must add the /3gb parameter to the
boot.ini file. This allows user applications to address 3 GB of virtual
memory and reserves 1 GB of virtual memory for the operating system.
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
> Hello all,
> I have a SQL2000 installation with Windows2003 Enterprise and 4 GB of
> system
> memory. SQL never uses more than 2GB of system memory. What is the
> correct
> configuration of the 3GB and PAE switches in the boot.ini file?
> --
> Roy Love
> SupportOnline.BIZ|||I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
setting AWE to the amount of memory in the server. You mentioned virtural
memory, I am talking about physical memory.
thanks,
--
Roy Love
SupportOnline.BIZ
"Jerry Spivey" wrote:
> Roy,
> From the SQL BOL:
> To enable Windows 2000 Advanced Server and Windows 2000 Datacenter Server
to
> support a 3-GB virtual address space, you must add the /3gb parameter to t
he
> boot.ini file. This allows user applications to address 3 GB of virtual
> memory and reserves 1 GB of virtual memory for the operating system.
> HTH
> Jerry
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:0F55F3B8-39E0-4C82-8C51-189DC271D915@.microsoft.com...
>
>|||Roy,
Might take a look at:
http://support.microsoft.com/defaul...;274750&sd=tech
and
http://support.microsoft.com/kb/283037/
HTH
Jerry
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...[vbcol=seagreen]
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
>|||If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB memo
ry. I think that 2Gb is
for the buffer pool (data cache, cached plans etc), and MemToLeave area is o
utside of that. So,
*possibly* you could tweak out a bit more using PAE and AWE:
Today (roughly):
BP: 1.7 GB
MemToLeave: 0.3 GB
With AWE and PAE:
BP: 2 GB
MemToLeave 0.3 GB
Here's a good place to learn more about how SQL Server uses memory, AWE etc.
:
http://blogs.msdn.com/slavao/
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...[vbcol=seagreen]
>I am running Windows2003 Server Enterprise, not 2K. SQL also mentions
> setting AWE to the amount of memory in the server. You mentioned virtural
> memory, I am talking about physical memory.
> thanks,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Jerry Spivey" wrote:
>|||Is Windows seeing the full 4GB?
Some raid cards (hot swap pci etc) can "steal" some memory unless you use
/PAE.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23BPfWr70FHA.3376@.TK2MSFTNGP14.phx.gbl...
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB
> memory. I think that 2Gb is for the buffer pool (data cache, cached plans
> etc), and MemToLeave area is outside of that. So, *possibly* you could
> tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE
> etc.: http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>|||Thanks Tibor,
I am running SQL2000 Enterprise Edition, not SE.
Regards,
--
Roy Love
SupportOnline.BIZ
"Tibor Karaszi" wrote:
> If you are using SQL Server 2000 SE, then SQL Server will not use > 2GB me
mory. I think that 2Gb is
> for the buffer pool (data cache, cached plans etc), and MemToLeave area is
outside of that. So,
> *possibly* you could tweak out a bit more using PAE and AWE:
> Today (roughly):
> BP: 1.7 GB
> MemToLeave: 0.3 GB
> With AWE and PAE:
> BP: 2 GB
> MemToLeave 0.3 GB
> Here's a good place to learn more about how SQL Server uses memory, AWE et
c.:
> http://blogs.msdn.com/slavao/
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
> news:98937CC7-FA07-4952-951A-132FD41E23F6@.microsoft.com...
>|||Then you need either the /3GB switch or PAE and AWE. Aside, all memory in Wi
ndows is virtual memory,
An application doesn't address memory directly, it goes by the OS memory man
ager. Here's a start:
http://support.microsoft.com/defaul...kb;en-us;274750
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RDL1912" <RDL1912@.discussions.microsoft.com> wrote in message
news:76402F72-A1B6-466F-802F-234A1033E0AE@.microsoft.com...[vbcol=seagreen]
> Thanks Tibor,
> I am running SQL2000 Enterprise Edition, not SE.
> Regards,
> --
> Roy Love
> SupportOnline.BIZ
>
> "Tibor Karaszi" wrote:
>
Correct Edition of Reporting Services
Hi,
We are in the process of replacing our Microsoft Access(.adp)/SQL2000 based reporting tool to ReportingServices/SQL2000 one. Our development team would be in charge of converting the existing Access based reports to Reporting Service format and and any new reports thereafter. Keeping that in mind which of the existing version(Standard, Enterprise, Developer) of Reporting Services would best suit our environment? The final picture would be something like all the reports will be residing on the Reporting server and it will be accessed by clients with the help of a custom reporting application(made in .net) that calls these reports based on user level permissions to these reports.
Will this be possible by using a Standard edition of RS?
Looking forward to your replies..
sk
Do you mean SQL 2005? I've never used SQL 2000 RS so I couldn't really comment.
|||No, i meant SQL2000. I know that RS is bundled into the SQL2005 installation media but as far as SQL2000 is concerned, it was only released quite some time after SQL Server was released. I have read in the help file that the Standard edition of SQL2000 does support the standard as well as enterprise edition of RS2000. Therefore i was looking for the correct edition that best suits our requirement which i have mentioned in my earlier post...
sk
|||Here is the feature mix information for SQL Server 2005 - it is applicable to SQL 2000 also with the exception of features that were new to 2005 (Report Builder, for example).
http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx
|||Thanks Carolyn for the link. So can i safely presume that i could deploy my reports created with Standard Reporting Services for my my users to access in a client-server setup?
Last But not least, I had downloaded the 120 days Eval copy of RS for SQL2000. Since my SQL2000 server is already licensed, should i need extra licensing to use Reporting services?
sk
|||You should be able to use the standard edition of SRS 2000 to accomplish what you require. The version that you are licensed for matches the version of SQL Server that you have. Developer edition is never licensed for production work.
If you are developing using VS 2005, you have access to the ReportViewer control even if you don't have SSRS 2005 in your environment. You could also embed your reports into your application using it. From your post I don't know if you are doing a WinForm or WebForm, but the ReportViewer control works well in either case. You could source data from your SQL Server 2000 instance, but I don't believe you will be able to display SRS 2000 reports from it directly.
You will need the Visual Studio 2003 environment for anyone you want to be able to create reports. That yet another big difference between SRS 2000 and SSRS 2005. SSRS 2005 does not require VS to be installed, it is capable of installing the pieces it requires.
RE the licensing, short answer: SRS is a component of SQL Server. Anywhere you are licensed to have SQL Server installed, you can also have SRS installed. Here is a page that describes some of the different scenarios:
http://www.microsoft.com/sql/prodinfo/previousversions/rs/howtolicensers.mspx
Regarding your eval copy, if you do not want an interruption of services, go to the link below and order your copy of SRS for S/H cost. Do it now, before the eval expires.
http://www.microsoft.com/sql/prodinfo/previousversions/rs/retailfulfillment.mspx
Make sure to get SP2 for SRS 2000 (http://www.microsoft.com/downloads/details.aspx?FamilyId=502C0D89-1308-4662-8F58-CEC55EF1235B&displaylang=en) as it expands the feature set (adding client printing) as well as fixes some bugs.
Good luck with your migration!
Larry Smithmier
|||Thanks for your input Larry.
So once i get the licensed copy of SRS2000, i would have to un-install the existing eval copy and install the licensed one?
If thats the case i would want to warn my developers against deploying anything on the server untill a licensed copy is avalable...
Would i have to re-install the client components too on the developers machines? And finally, would i have to apply the SRS2000 SP2 to the developers machines too?
sk
|||
I believe that installing the full version over the evaluation should upgrade the instance in-place. You should not have to uninstall the eval copy.
Let your developers deploy at will. I believe that the installation will upgrade your version. The worst case scenario would be that your developers would need to re-deploy the reports after you uninstalled and reinstalled.
Yes, you would want to apply SP2 to development boxes also.
Larry Smithmier
sqlCorrect Edition of Reporting Services
Hi,
We are in the process of replacing our Microsoft Access(.adp)/SQL2000 based reporting tool to ReportingServices/SQL2000 one. Our development team would be in charge of converting the existing Access based reports to Reporting Service format and and any new reports thereafter. Keeping that in mind which of the existing version(Standard, Enterprise, Developer) of Reporting Services would best suit our environment? The final picture would be something like all the reports will be residing on the Reporting server and it will be accessed by clients with the help of a custom reporting application(made in .net) that calls these reports based on user level permissions to these reports.
Will this be possible by using a Standard edition of RS?
Looking forward to your replies..
sk
Do you mean SQL 2005? I've never used SQL 2000 RS so I couldn't really comment.
|||No, i meant SQL2000. I know that RS is bundled into the SQL2005 installation media but as far as SQL2000 is concerned, it was only released quite some time after SQL Server was released. I have read in the help file that the Standard edition of SQL2000 does support the standard as well as enterprise edition of RS2000. Therefore i was looking for the correct edition that best suits our requirement which i have mentioned in my earlier post...
sk
|||Here is the feature mix information for SQL Server 2005 - it is applicable to SQL 2000 also with the exception of features that were new to 2005 (Report Builder, for example).
http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx
|||Thanks Carolyn for the link. So can i safely presume that i could deploy my reports created with Standard Reporting Services for my my users to access in a client-server setup?
Last But not least, I had downloaded the 120 days Eval copy of RS for SQL2000. Since my SQL2000 server is already licensed, should i need extra licensing to use Reporting services?
sk
|||You should be able to use the standard edition of SRS 2000 to accomplish what you require. The version that you are licensed for matches the version of SQL Server that you have. Developer edition is never licensed for production work.
If you are developing using VS 2005, you have access to the ReportViewer control even if you don't have SSRS 2005 in your environment. You could also embed your reports into your application using it. From your post I don't know if you are doing a WinForm or WebForm, but the ReportViewer control works well in either case. You could source data from your SQL Server 2000 instance, but I don't believe you will be able to display SRS 2000 reports from it directly.
You will need the Visual Studio 2003 environment for anyone you want to be able to create reports. That yet another big difference between SRS 2000 and SSRS 2005. SSRS 2005 does not require VS to be installed, it is capable of installing the pieces it requires.
RE the licensing, short answer: SRS is a component of SQL Server. Anywhere you are licensed to have SQL Server installed, you can also have SRS installed. Here is a page that describes some of the different scenarios:
http://www.microsoft.com/sql/prodinfo/previousversions/rs/howtolicensers.mspx
Regarding your eval copy, if you do not want an interruption of services, go to the link below and order your copy of SRS for S/H cost. Do it now, before the eval expires.
http://www.microsoft.com/sql/prodinfo/previousversions/rs/retailfulfillment.mspx
Make sure to get SP2 for SRS 2000 (http://www.microsoft.com/downloads/details.aspx?FamilyId=502C0D89-1308-4662-8F58-CEC55EF1235B&displaylang=en) as it expands the feature set (adding client printing) as well as fixes some bugs.
Good luck with your migration!
Larry Smithmier
|||Thanks for your input Larry.
So once i get the licensed copy of SRS2000, i would have to un-install the existing eval copy and install the licensed one?
If thats the case i would want to warn my developers against deploying anything on the server untill a licensed copy is avalable...
Would i have to re-install the client components too on the developers machines? And finally, would i have to apply the SRS2000 SP2 to the developers machines too?
sk
|||
I believe that installing the full version over the evaluation should upgrade the instance in-place. You should not have to uninstall the eval copy.
Let your developers deploy at will. I believe that the installation will upgrade your version. The worst case scenario would be that your developers would need to re-deploy the reports after you uninstalled and reinstalled.
Yes, you would want to apply SP2 to development boxes also.
Larry Smithmier
Correct Edition of Reporting Services
Hi,
We are in the process of replacing our Microsoft Access(.adp)/SQL2000 based reporting tool to ReportingServices/SQL2000 one. Our development team would be in charge of converting the existing Access based reports to Reporting Service format and and any new reports thereafter. Keeping that in mind which of the existing version(Standard, Enterprise, Developer) of Reporting Services would best suit our environment? The final picture would be something like all the reports will be residing on the Reporting server and it will be accessed by clients with the help of a custom reporting application(made in .net) that calls these reports based on user level permissions to these reports.
Will this be possible by using a Standard edition of RS?
Looking forward to your replies..
sk
Do you mean SQL 2005? I've never used SQL 2000 RS so I couldn't really comment.
|||No, i meant SQL2000. I know that RS is bundled into the SQL2005 installation media but as far as SQL2000 is concerned, it was only released quite some time after SQL Server was released. I have read in the help file that the Standard edition of SQL2000 does support the standard as well as enterprise edition of RS2000. Therefore i was looking for the correct edition that best suits our requirement which i have mentioned in my earlier post...
sk
|||Here is the feature mix information for SQL Server 2005 - it is applicable to SQL 2000 also with the exception of features that were new to 2005 (Report Builder, for example).
http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx
|||Thanks Carolyn for the link. So can i safely presume that i could deploy my reports created with Standard Reporting Services for my my users to access in a client-server setup?
Last But not least, I had downloaded the 120 days Eval copy of RS for SQL2000. Since my SQL2000 server is already licensed, should i need extra licensing to use Reporting services?
sk
|||You should be able to use the standard edition of SRS 2000 to accomplish what you require. The version that you are licensed for matches the version of SQL Server that you have. Developer edition is never licensed for production work.
If you are developing using VS 2005, you have access to the ReportViewer control even if you don't have SSRS 2005 in your environment. You could also embed your reports into your application using it. From your post I don't know if you are doing a WinForm or WebForm, but the ReportViewer control works well in either case. You could source data from your SQL Server 2000 instance, but I don't believe you will be able to display SRS 2000 reports from it directly.
You will need the Visual Studio 2003 environment for anyone you want to be able to create reports. That yet another big difference between SRS 2000 and SSRS 2005. SSRS 2005 does not require VS to be installed, it is capable of installing the pieces it requires.
RE the licensing, short answer: SRS is a component of SQL Server. Anywhere you are licensed to have SQL Server installed, you can also have SRS installed. Here is a page that describes some of the different scenarios:
http://www.microsoft.com/sql/prodinfo/previousversions/rs/howtolicensers.mspx
Regarding your eval copy, if you do not want an interruption of services, go to the link below and order your copy of SRS for S/H cost. Do it now, before the eval expires.
http://www.microsoft.com/sql/prodinfo/previousversions/rs/retailfulfillment.mspx
Make sure to get SP2 for SRS 2000 (http://www.microsoft.com/downloads/details.aspx?FamilyId=502C0D89-1308-4662-8F58-CEC55EF1235B&displaylang=en) as it expands the feature set (adding client printing) as well as fixes some bugs.
Good luck with your migration!
Larry Smithmier
|||Thanks for your input Larry.
So once i get the licensed copy of SRS2000, i would have to un-install the existing eval copy and install the licensed one?
If thats the case i would want to warn my developers against deploying anything on the server untill a licensed copy is avalable...
Would i have to re-install the client components too on the developers machines? And finally, would i have to apply the SRS2000 SP2 to the developers machines too?
sk
|||
I believe that installing the full version over the evaluation should upgrade the instance in-place. You should not have to uninstall the eval copy.
Let your developers deploy at will. I believe that the installation will upgrade your version. The worst case scenario would be that your developers would need to re-deploy the reports after you uninstalled and reinstalled.
Yes, you would want to apply SP2 to development boxes also.
Larry Smithmier
Sunday, March 11, 2012
copying databases from one server (win2K) to another (win2k3)
Hello All,
I am a SQL server newbie, so please try to answer in simple terms. I
am trying to copy databases from a SQL 2000 (Win2k) to another SQL
2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
getting the familiar "Failed to create OMWWIZE share" error.
I've set up my source server to start up with the 'System Account' and
my destination server to start up with my Windows account that has
administrative privileges on that machine.
After reading up on several froums, SQL Server Books online...I came
to know that backup/restore is a wonderful option, but I don't have
the same drive specifications on the two servers and also need some
step by step instructions on how to back up the databases on the
source server and restore the same in the destination server.
Thanks to you all in advance for the help.
Ram.I think that wizard causes more problems than it solves. Have a look at
these:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues
Andrew J. Kelly SQL MVP
"RAM GANESAN" <ramganesan@.gmail.com> wrote in message
news:2dca7102.0407301057.445d4d17@.posting.google.com...
> Hello All,
> I am a SQL server newbie, so please try to answer in simple terms. I
> am trying to copy databases from a SQL 2000 (Win2k) to another SQL
> 2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
> getting the familiar "Failed to create OMWWIZE share" error.
> I've set up my source server to start up with the 'System Account' and
> my destination server to start up with my Windows account that has
> administrative privileges on that machine.
> After reading up on several froums, SQL Server Books online...I came
> to know that backup/restore is a wonderful option, but I don't have
> the same drive specifications on the two servers and also need some
> step by step instructions on how to back up the databases on the
> source server and restore the same in the destination server.
> Thanks to you all in advance for the help.
> Ram.|||Easiest way is probably to restore a backup to the other server
or detach/attach
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default.aspx?kbid=314546
INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/defaul...b;EN-US;q224071
For tips on using the Copy database wizard
INF: Understanding and Troubleshooting the Copy Database Wizard in SQL
Server 2000
http://support.microsoft.com/defaul...b;en-us;Q274463
Also check out
INF: How To Transfer Logins and Passwords Between SQL Servers
http://support.microsoft.com/defaul...b;en-us;Q246133
PRB: User Logon and/or Permission Errors After Restoring Dump
http://support.microsoft.com/defaul...b;en-us;Q168001
INF: How to Resolve Permission Issues When a Database is Moved Between SQL
Servers
http://support.microsoft.com/defaul...b;en-us;Q240872
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://support.microsoft.com/defaul...b;en-us;Q274188
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"RAM GANESAN" <ramganesan@.gmail.com> wrote in message
news:2dca7102.0407301057.445d4d17@.posting.google.com...
> Hello All,
> I am a SQL server newbie, so please try to answer in simple terms. I
> am trying to copy databases from a SQL 2000 (Win2k) to another SQL
> 2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
> getting the familiar "Failed to create OMWWIZE share" error.
> I've set up my source server to start up with the 'System Account' and
> my destination server to start up with my Windows account that has
> administrative privileges on that machine.
> After reading up on several froums, SQL Server Books online...I came
> to know that backup/restore is a wonderful option, but I don't have
> the same drive specifications on the two servers and also need some
> step by step instructions on how to back up the databases on the
> source server and restore the same in the destination server.
> Thanks to you all in advance for the help.
> Ram.
I am a SQL server newbie, so please try to answer in simple terms. I
am trying to copy databases from a SQL 2000 (Win2k) to another SQL
2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
getting the familiar "Failed to create OMWWIZE share" error.
I've set up my source server to start up with the 'System Account' and
my destination server to start up with my Windows account that has
administrative privileges on that machine.
After reading up on several froums, SQL Server Books online...I came
to know that backup/restore is a wonderful option, but I don't have
the same drive specifications on the two servers and also need some
step by step instructions on how to back up the databases on the
source server and restore the same in the destination server.
Thanks to you all in advance for the help.
Ram.I think that wizard causes more problems than it solves. Have a look at
these:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues
Andrew J. Kelly SQL MVP
"RAM GANESAN" <ramganesan@.gmail.com> wrote in message
news:2dca7102.0407301057.445d4d17@.posting.google.com...
> Hello All,
> I am a SQL server newbie, so please try to answer in simple terms. I
> am trying to copy databases from a SQL 2000 (Win2k) to another SQL
> 2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
> getting the familiar "Failed to create OMWWIZE share" error.
> I've set up my source server to start up with the 'System Account' and
> my destination server to start up with my Windows account that has
> administrative privileges on that machine.
> After reading up on several froums, SQL Server Books online...I came
> to know that backup/restore is a wonderful option, but I don't have
> the same drive specifications on the two servers and also need some
> step by step instructions on how to back up the databases on the
> source server and restore the same in the destination server.
> Thanks to you all in advance for the help.
> Ram.|||Easiest way is probably to restore a backup to the other server
or detach/attach
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default.aspx?kbid=314546
INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/defaul...b;EN-US;q224071
For tips on using the Copy database wizard
INF: Understanding and Troubleshooting the Copy Database Wizard in SQL
Server 2000
http://support.microsoft.com/defaul...b;en-us;Q274463
Also check out
INF: How To Transfer Logins and Passwords Between SQL Servers
http://support.microsoft.com/defaul...b;en-us;Q246133
PRB: User Logon and/or Permission Errors After Restoring Dump
http://support.microsoft.com/defaul...b;en-us;Q168001
INF: How to Resolve Permission Issues When a Database is Moved Between SQL
Servers
http://support.microsoft.com/defaul...b;en-us;Q240872
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://support.microsoft.com/defaul...b;en-us;Q274188
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"RAM GANESAN" <ramganesan@.gmail.com> wrote in message
news:2dca7102.0407301057.445d4d17@.posting.google.com...
> Hello All,
> I am a SQL server newbie, so please try to answer in simple terms. I
> am trying to copy databases from a SQL 2000 (Win2k) to another SQL
> 2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
> getting the familiar "Failed to create OMWWIZE share" error.
> I've set up my source server to start up with the 'System Account' and
> my destination server to start up with my Windows account that has
> administrative privileges on that machine.
> After reading up on several froums, SQL Server Books online...I came
> to know that backup/restore is a wonderful option, but I don't have
> the same drive specifications on the two servers and also need some
> step by step instructions on how to back up the databases on the
> source server and restore the same in the destination server.
> Thanks to you all in advance for the help.
> Ram.
copying databases from one server (win2K) to another (win2k3)
Hello All,
I am a SQL server newbie, so please try to answer in simple terms. I
am trying to copy databases from a SQL 2000 (Win2k) to another SQL
2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
getting the familiar "Failed to create OMWWIZE share" error.
I've set up my source server to start up with the 'System Account' and
my destination server to start up with my Windows account that has
administrative privileges on that machine.
After reading up on several froums, SQL Server Books online...I came
to know that backup/restore is a wonderful option, but I don't have
the same drive specifications on the two servers and also need some
step by step instructions on how to back up the databases on the
source server and restore the same in the destination server.
Thanks to you all in advance for the help.
Ram.
I think that wizard causes more problems than it solves. Have a look at
these:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues
Andrew J. Kelly SQL MVP
"RAM GANESAN" <ramganesan@.gmail.com> wrote in message
news:2dca7102.0407301057.445d4d17@.posting.google.c om...
> Hello All,
> I am a SQL server newbie, so please try to answer in simple terms. I
> am trying to copy databases from a SQL 2000 (Win2k) to another SQL
> 2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
> getting the familiar "Failed to create OMWWIZE share" error.
> I've set up my source server to start up with the 'System Account' and
> my destination server to start up with my Windows account that has
> administrative privileges on that machine.
> After reading up on several froums, SQL Server Books online...I came
> to know that backup/restore is a wonderful option, but I don't have
> the same drive specifications on the two servers and also need some
> step by step instructions on how to back up the databases on the
> source server and restore the same in the destination server.
> Thanks to you all in advance for the help.
> Ram.
|||Easiest way is probably to restore a backup to the other server
or detach/attach
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default.aspx?kbid=314546
INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/default...;EN-US;q224071
For tips on using the Copy database wizard
INF: Understanding and Troubleshooting the Copy Database Wizard in SQL
Server 2000
http://support.microsoft.com/default...;en-us;Q274463
Also check out
INF: How To Transfer Logins and Passwords Between SQL Servers
http://support.microsoft.com/default...;en-us;Q246133
PRB: User Logon and/or Permission Errors After Restoring Dump
http://support.microsoft.com/default...;en-us;Q168001
INF: How to Resolve Permission Issues When a Database is Moved Between SQL
Servers
http://support.microsoft.com/default...;en-us;Q240872
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://support.microsoft.com/default...;en-us;Q274188
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"RAM GANESAN" <ramganesan@.gmail.com> wrote in message
news:2dca7102.0407301057.445d4d17@.posting.google.c om...
> Hello All,
> I am a SQL server newbie, so please try to answer in simple terms. I
> am trying to copy databases from a SQL 2000 (Win2k) to another SQL
> 2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
> getting the familiar "Failed to create OMWWIZE share" error.
> I've set up my source server to start up with the 'System Account' and
> my destination server to start up with my Windows account that has
> administrative privileges on that machine.
> After reading up on several froums, SQL Server Books online...I came
> to know that backup/restore is a wonderful option, but I don't have
> the same drive specifications on the two servers and also need some
> step by step instructions on how to back up the databases on the
> source server and restore the same in the destination server.
> Thanks to you all in advance for the help.
> Ram.
I am a SQL server newbie, so please try to answer in simple terms. I
am trying to copy databases from a SQL 2000 (Win2k) to another SQL
2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
getting the familiar "Failed to create OMWWIZE share" error.
I've set up my source server to start up with the 'System Account' and
my destination server to start up with my Windows account that has
administrative privileges on that machine.
After reading up on several froums, SQL Server Books online...I came
to know that backup/restore is a wonderful option, but I don't have
the same drive specifications on the two servers and also need some
step by step instructions on how to back up the databases on the
source server and restore the same in the destination server.
Thanks to you all in advance for the help.
Ram.
I think that wizard causes more problems than it solves. Have a look at
these:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues
Andrew J. Kelly SQL MVP
"RAM GANESAN" <ramganesan@.gmail.com> wrote in message
news:2dca7102.0407301057.445d4d17@.posting.google.c om...
> Hello All,
> I am a SQL server newbie, so please try to answer in simple terms. I
> am trying to copy databases from a SQL 2000 (Win2k) to another SQL
> 2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
> getting the familiar "Failed to create OMWWIZE share" error.
> I've set up my source server to start up with the 'System Account' and
> my destination server to start up with my Windows account that has
> administrative privileges on that machine.
> After reading up on several froums, SQL Server Books online...I came
> to know that backup/restore is a wonderful option, but I don't have
> the same drive specifications on the two servers and also need some
> step by step instructions on how to back up the databases on the
> source server and restore the same in the destination server.
> Thanks to you all in advance for the help.
> Ram.
|||Easiest way is probably to restore a backup to the other server
or detach/attach
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default.aspx?kbid=314546
INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/default...;EN-US;q224071
For tips on using the Copy database wizard
INF: Understanding and Troubleshooting the Copy Database Wizard in SQL
Server 2000
http://support.microsoft.com/default...;en-us;Q274463
Also check out
INF: How To Transfer Logins and Passwords Between SQL Servers
http://support.microsoft.com/default...;en-us;Q246133
PRB: User Logon and/or Permission Errors After Restoring Dump
http://support.microsoft.com/default...;en-us;Q168001
INF: How to Resolve Permission Issues When a Database is Moved Between SQL
Servers
http://support.microsoft.com/default...;en-us;Q240872
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://support.microsoft.com/default...;en-us;Q274188
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"RAM GANESAN" <ramganesan@.gmail.com> wrote in message
news:2dca7102.0407301057.445d4d17@.posting.google.c om...
> Hello All,
> I am a SQL server newbie, so please try to answer in simple terms. I
> am trying to copy databases from a SQL 2000 (Win2k) to another SQL
> 2000 (Win2k3). I am trying to use the Copy Database Wizard and end up
> getting the familiar "Failed to create OMWWIZE share" error.
> I've set up my source server to start up with the 'System Account' and
> my destination server to start up with my Windows account that has
> administrative privileges on that machine.
> After reading up on several froums, SQL Server Books online...I came
> to know that backup/restore is a wonderful option, but I don't have
> the same drive specifications on the two servers and also need some
> step by step instructions on how to back up the databases on the
> source server and restore the same in the destination server.
> Thanks to you all in advance for the help.
> Ram.
Copying Database table to another Database
I am using Visual Studio 2005 to connect to a database on a remote SQL2000 server. I need to copy a table in a database on my local machine up to the server. How can I do that?
Thank you,
Do you have enterprise manager or sql management studio?
If so do use the Import/Export wizard to copy the table from A to B.
|||no - I have Access 2007 and it is nothing like Access 2000 which made this act easy
|||
Part of my problem is that I am using Vista and it is giving me fits.
|||This is "long ago at school" kind of knowledge for me. But can't u connect the sql server to your access database and copy the data across from within access?
|||Finally got it - the adp setup in Access 2007 is completely different but you are correct it does work and actually quite well - now that I learned how to use it. The brain always stops with learning incomplete.
THank you
Thursday, March 8, 2012
Copying data from SQL2000 to DB2 8.1
I have to setup some scheduled tasks to copy 3-4 tables from an
SQL2000 database to DB2 v. 8.1.
The job must run every night replacing all data.
How can this be done - with standard utilities??
Please be exact - I'm new to this.
Thank for any help.
/Jep"Jep" <dontspam_jep@.jepweb.dk> wrote in message
news:d3g1kvk7p4ppe932pa5a8s7ncegruk6act@.4ax.com...
>
> I have to setup some scheduled tasks to copy 3-4 tables from an
> SQL2000 database to DB2 v. 8.1.
> The job must run every night replacing all data.
> How can this be done - with standard utilities??
> Please be exact - I'm new to this.
>
> Thank for any help.
> /Jep
Some possibilites are BCP, DTS and a linked server. BCP is used to copy
table data to a flat file - the file could then be transferred to the DB2
box and loaded with a similar DB2 utility. DTS is much more complex, but
includes workflow and can transfer data between many different sources. A
linked server would allow you to reference a DB2 table directly from SQL
Server, so you could do a simple INSERT ... SELECT...
All these options are covered in Books Online. If you don't have much
experience of using these tools, I'd suggest looking at BCP as a first
option - it's a command-line tool, and it's usually straightforward to use.
Whatever option you choose, you can use SQL Agent to schedule a job in
SQL2000 - see "Scheduling Jobs" in Books Online.
Simon
Wednesday, March 7, 2012
Copying a project. How?
We recently migrated to SQL2005 and have moved all OLAP databases to the new server. I need to create new OLAP databases. In SQL2000, just a copy would do it, but I am having problem in 2005. I tried to script the database as 'create' or even created an empty one and try to change it by 'alter' from a valid DB, but no luck (XMLA file was modified to have the new names).
Any pointers, suggestion would be appreciated. I know how to change the DataSource and DataView later, just need to know how to copy one!!!!
Also please let me know what tool is used (Management Studio, Visual Studio, etc...)
Thanks in advance!
Then made a new DataSource pointing to the right source and changed the DSV in XML to point to it <-- Great
Problem now is that, it is throwing and error that The 'Role' with 'ID' ='suchandsuch' doesn't exist in the collection when I go to build it. I saw this Role in the DataSource when viewed in XML and obviously can change it, but will not compile even when changed to a more previleged role. Same error!
The other OLAP database runs fine.
Any comments, suggestion will be appreciated as always, as I hope this info will help the next person.
noorbakhsh|||Got it. The above will fix the problem except we had a removed user which I had to remove from users in roles manually. Also the database I copied was corrupted so when I re-did it it worked fine.
I hope this helps others!
noorbakhsh|||One more follow-up since the other stuff had errors and there was an easier way:
Any pointers, suggestion would be appreciated. I know how to change the DataSource and DataView later, just need to know how to copy one!!!!
Also please let me know what tool is used (Management Studio, Visual Studio, etc...)
Thanks in advance!
There is a special project in BIDS where you can reverse engineer a SSAS 2005 database.
If you have a BIDS project with a cube you can choose to save the whole project under a new name.
HTH
Thomas Ivarsson
|||I used BIDS, made a new 'Import Analysis Services 9.0 Database' from the template and imported a working database with everything. <-- Great.Then made a new DataSource pointing to the right source and changed the DSV in XML to point to it <-- Great
Problem now is that, it is throwing and error that The 'Role' with 'ID' ='suchandsuch' doesn't exist in the collection when I go to build it. I saw this Role in the DataSource when viewed in XML and obviously can change it, but will not compile even when changed to a more previleged role. Same error!
The other OLAP database runs fine.
Any comments, suggestion will be appreciated as always, as I hope this info will help the next person.
noorbakhsh|||Got it. The above will fix the problem except we had a removed user which I had to remove from users in roles manually. Also the database I copied was corrupted so when I re-did it it worked fine.
I hope this helps others!
noorbakhsh|||One more follow-up since the other stuff had errors and there was an easier way:
I used BIDS, made a new
'Import Analysis Services 9.0 Database' from the template with the new databse name and imported
a working database with everything. <-- Great.
Then I just right-clicked on the DataSource/View Designer and 'edit' the connection string pointing to the new DataBase.
Right clicked on the database/properties and changed the deployment parameters
Deploy - Done
I hope this helps!!! - It should :)
noorbakhsh
Friday, February 24, 2012
Copy to SQL2000 made command slow?
Hi,
I took a copy of a SQL7-Database with DTS to an SQL2000 Server.
The new copy of the SQL2000 runns fine. Also the application useing the new
DB.
But some of the SQL Commands became very solw (<1s => >200s).
Is it neceserry to optimize all the SQL-Commands - what e horror.
Thanks a lot
Andreas
Here the commands and the tabledef:
SELECT AG.GuidID, AG.Bezeichnung1 FROM
(Artikel A INNER JOIN StrukturArtikel SA ON A.GuidID = SA.ArtikelID)
INNER JOIN Attributgruppen AG ON A.AttributGruppenID = AG.GuidID
GROUP BY AG.GuidID, AG.Bezeichnung1, SA.StrukturKatalogID
HAVING SA.StrukturKatalogID = '5269C032AB1011D787D20000CB531E4D' ORDER BY
AG.Bezeichnung1
=== Aufbau Tabelle A======== CREATE TABLE [dbo].[Artikel] (
[GuidID] [char] (32) NOT NULL ,
[ArtikelNr] [varchar] (32) NULL ,
[AttributGruppenId] [char] (32) NULL ,
[VariationsAttribut] [char] (32) NULL ,
[Varianz] [varchar] (50) NULL ,
[Bezeichnung1] [varchar] (80) NULL ,
[BeschreibungLang1] [text] NULL ,
[VariationsBlockID] [char] (32) NULL ,
[Bezeichnung2] [varchar] (80) NULL ,
[Bezeichnung3] [varchar] (80) NULL ,
[Bezeichnung4] [varchar] (80) NULL ,
[Bezeichnung5] [varchar] (80) NULL ,
[BeschreibungLang2] [text] NULL ,
[BeschreibungLang3] [text] NULL ,
[BeschreibungLang4] [text] NULL ,
[BeschreibungLang5] [text] NULL ,
[anlage_datum] [datetime] NULL ,
[anlage_zeichen] [char] (16) NULL ,
[aender_datum] [datetime] NULL ,
[aender_zeichen] [char] (16) NULL ,
[ArtikelNrLief1] [varchar] (32) NULL ,
[Lieferant1] [varchar] (8) NULL ,
[ArtikelNrLief2] [varchar] (32) NULL ,
[Lieferant2] [varchar] (8) NULL ,
[ArtikelNrLief3] [varchar] (32) NULL ,
[Lieferant3] [varchar] (8) NULL ,
[Freigabe1] [tinyint] NULL ,
[Freigabe2] [tinyint] NULL ,
[Freigabe3] [tinyint] NULL ,
[Tag1] [varchar] (16) NULL ,
[Tag2] [varchar] (16) NULL
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
CREATE INDEX [ArtikelNr] ON [dbo].[Artikel]([ArtikelNr]) WITH FILLFACTOR
= 90 ON [PRIMARY]
CREATE INDEX [VariationsAttribut] ON [dbo].[Artikel]([VariationsAttribut])
WITH FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [AttributGruppenId] ON [dbo].[Artikel]([AttributGruppenId])
WITH FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [ArtikelNrLief1] ON [dbo].[Artikel]([ArtikelNrLief1]) WITH
FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [ArtikelNrLief2] ON [dbo].[Artikel]([ArtikelNrLief2]) WITH
FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [ArtikelNrLief3] ON [dbo].[Artikel]([ArtikelNrLief3]) WITH
FILLFACTOR = 90 ON [PRIMARY]
=== Aufbau Tabelle AG======== CREATE TABLE [dbo].[AttributGruppen] (
[GuidID] [char] (32) NOT NULL ,
[Reihenfolge] [int] NULL ,
[Ebene] [int] NULL ,
[Bezeichnung1] [varchar] (1024) NULL ,
[Bezeichnung2] [varchar] (1024) NULL ,
[Bezeichnung3] [varchar] (1024) NULL ,
[Bezeichnung4] [varchar] (1024) NULL ,
[Bezeichnung5] [varchar] (1024) NULL ,
[anlage_datum] [datetime] NULL ,
[anlage_zeichen] [char] (16) NULL ,
[aender_datum] [datetime] NULL ,
[aender_zeichen] [char] (16) NULL ,
[AttributGruppenNummer] [varchar] (15) NULL
) ON [PRIMARY]
CREATE INDEX [Ebene] ON [dbo].[AttributGruppen]([Ebene]) WITH FILLFACTOR
= 90 ON [PRIMARY]
=== Aufbau Tabelle SA======== CREATE TABLE [dbo].[StrukturArtikel] (
[StrukturID] [char] (32) NOT NULL ,
[StrukturKatalogID] [char] (32) NOT NULL ,
[ArtikelID] [char] (32) NOT NULL ,
[Katalogspezifisch] [bit] NULL ,
[Reihenfolge] [int] NULL ,
[Parent] [char] (32) NULL ,
[Ebene] [int] NULL ,
[anlage_datum] [datetime] NULL ,
[anlage_zeichen] [char] (16) NULL ,
[aender_datum] [datetime] NULL ,
[aender_zeichen] [char] (16) NULL
) ON [PRIMARY]
CREATE INDEX [ArtikelID] ON [dbo].[StrukturArtikel]([ArtikelID]) WITH
FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [Parent] ON [dbo].[StrukturArtikel]([Parent]) WITH
FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [StrukturID] ON [dbo].[StrukturArtikel]([StrukturID]) WITH
FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [StrukturKatalogID] ON
[dbo].[StrukturArtikel]([StrukturKatalogID]) WITH FILLFACTOR = 90 ON
[PRIMARY]Did you update stats after copying everything over? When
you say new application, you mean it was only converted
for SQL2K? or are there logic changes also? Compare
that all indexing is carried over, if it was supposed to
be!?! Beyond that, give SQL Profiler a shot to see the
exact slow statements and take it from there... Bruce
>--Original Message--
>Hi,
>I took a copy of a SQL7-Database with DTS to an SQL2000
Server.
>The new copy of the SQL2000 runns fine. Also the
application useing the new
>DB.
>But some of the SQL Commands became very solw (<1s =>
>200s).
>Is it neceserry to optimize all the SQL-Commands - what
e horror.
>Thanks a lot
>Andreas
>
>Here the commands and the tabledef:
>SELECT AG.GuidID, AG.Bezeichnung1 FROM
>(Artikel A INNER JOIN StrukturArtikel SA ON A.GuidID =SA.ArtikelID)
>INNER JOIN Attributgruppen AG ON A.AttributGruppenID =AG.GuidID
>GROUP BY AG.GuidID, AG.Bezeichnung1, SA.StrukturKatalogID
>HAVING SA.StrukturKatalogID
= '5269C032AB1011D787D20000CB531E4D' ORDER BY
>AG.Bezeichnung1
>
>=== Aufbau Tabelle A========>CREATE TABLE [dbo].[Artikel] (
> [GuidID] [char] (32) NOT NULL ,
> [ArtikelNr] [varchar] (32) NULL ,
> [AttributGruppenId] [char] (32) NULL ,
> [VariationsAttribut] [char] (32) NULL ,
> [Varianz] [varchar] (50) NULL ,
> [Bezeichnung1] [varchar] (80) NULL ,
> [BeschreibungLang1] [text] NULL ,
> [VariationsBlockID] [char] (32) NULL ,
> [Bezeichnung2] [varchar] (80) NULL ,
> [Bezeichnung3] [varchar] (80) NULL ,
> [Bezeichnung4] [varchar] (80) NULL ,
> [Bezeichnung5] [varchar] (80) NULL ,
> [BeschreibungLang2] [text] NULL ,
> [BeschreibungLang3] [text] NULL ,
> [BeschreibungLang4] [text] NULL ,
> [BeschreibungLang5] [text] NULL ,
> [anlage_datum] [datetime] NULL ,
> [anlage_zeichen] [char] (16) NULL ,
> [aender_datum] [datetime] NULL ,
> [aender_zeichen] [char] (16) NULL ,
> [ArtikelNrLief1] [varchar] (32) NULL ,
> [Lieferant1] [varchar] (8) NULL ,
> [ArtikelNrLief2] [varchar] (32) NULL ,
> [Lieferant2] [varchar] (8) NULL ,
> [ArtikelNrLief3] [varchar] (32) NULL ,
> [Lieferant3] [varchar] (8) NULL ,
> [Freigabe1] [tinyint] NULL ,
> [Freigabe2] [tinyint] NULL ,
> [Freigabe3] [tinyint] NULL ,
> [Tag1] [varchar] (16) NULL ,
> [Tag2] [varchar] (16) NULL
>) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
> CREATE INDEX [ArtikelNr] ON [dbo].[Artikel]
([ArtikelNr]) WITH FILLFACTOR
>= 90 ON [PRIMARY]
> CREATE INDEX [VariationsAttribut] ON [dbo].[Artikel]
([VariationsAttribut])
>WITH FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [AttributGruppenId] ON [dbo].[Artikel]
([AttributGruppenId])
>WITH FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [ArtikelNrLief1] ON [dbo].[Artikel]
([ArtikelNrLief1]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [ArtikelNrLief2] ON [dbo].[Artikel]
([ArtikelNrLief2]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [ArtikelNrLief3] ON [dbo].[Artikel]
([ArtikelNrLief3]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
>
>=== Aufbau Tabelle AG========>CREATE TABLE [dbo].[AttributGruppen] (
> [GuidID] [char] (32) NOT NULL ,
> [Reihenfolge] [int] NULL ,
> [Ebene] [int] NULL ,
> [Bezeichnung1] [varchar] (1024) NULL ,
> [Bezeichnung2] [varchar] (1024) NULL ,
> [Bezeichnung3] [varchar] (1024) NULL ,
> [Bezeichnung4] [varchar] (1024) NULL ,
> [Bezeichnung5] [varchar] (1024) NULL ,
> [anlage_datum] [datetime] NULL ,
> [anlage_zeichen] [char] (16) NULL ,
> [aender_datum] [datetime] NULL ,
> [aender_zeichen] [char] (16) NULL ,
> [AttributGruppenNummer] [varchar] (15) NULL
>) ON [PRIMARY]
> CREATE INDEX [Ebene] ON [dbo].[AttributGruppen]
([Ebene]) WITH FILLFACTOR
>= 90 ON [PRIMARY]
>
>=== Aufbau Tabelle SA========>CREATE TABLE [dbo].[StrukturArtikel] (
> [StrukturID] [char] (32) NOT NULL ,
> [StrukturKatalogID] [char] (32) NOT NULL ,
> [ArtikelID] [char] (32) NOT NULL ,
> [Katalogspezifisch] [bit] NULL ,
> [Reihenfolge] [int] NULL ,
> [Parent] [char] (32) NULL ,
> [Ebene] [int] NULL ,
> [anlage_datum] [datetime] NULL ,
> [anlage_zeichen] [char] (16) NULL ,
> [aender_datum] [datetime] NULL ,
> [aender_zeichen] [char] (16) NULL
>) ON [PRIMARY]
> CREATE INDEX [ArtikelID] ON [dbo].[StrukturArtikel]
([ArtikelID]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [Parent] ON [dbo].[StrukturArtikel]
([Parent]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [StrukturID] ON [dbo].[StrukturArtikel]
([StrukturID]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [StrukturKatalogID] ON
>[dbo].[StrukturArtikel]([StrukturKatalogID]) WITH
FILLFACTOR = 90 ON
>[PRIMARY]
>
>.
>
I took a copy of a SQL7-Database with DTS to an SQL2000 Server.
The new copy of the SQL2000 runns fine. Also the application useing the new
DB.
But some of the SQL Commands became very solw (<1s => >200s).
Is it neceserry to optimize all the SQL-Commands - what e horror.
Thanks a lot
Andreas
Here the commands and the tabledef:
SELECT AG.GuidID, AG.Bezeichnung1 FROM
(Artikel A INNER JOIN StrukturArtikel SA ON A.GuidID = SA.ArtikelID)
INNER JOIN Attributgruppen AG ON A.AttributGruppenID = AG.GuidID
GROUP BY AG.GuidID, AG.Bezeichnung1, SA.StrukturKatalogID
HAVING SA.StrukturKatalogID = '5269C032AB1011D787D20000CB531E4D' ORDER BY
AG.Bezeichnung1
=== Aufbau Tabelle A======== CREATE TABLE [dbo].[Artikel] (
[GuidID] [char] (32) NOT NULL ,
[ArtikelNr] [varchar] (32) NULL ,
[AttributGruppenId] [char] (32) NULL ,
[VariationsAttribut] [char] (32) NULL ,
[Varianz] [varchar] (50) NULL ,
[Bezeichnung1] [varchar] (80) NULL ,
[BeschreibungLang1] [text] NULL ,
[VariationsBlockID] [char] (32) NULL ,
[Bezeichnung2] [varchar] (80) NULL ,
[Bezeichnung3] [varchar] (80) NULL ,
[Bezeichnung4] [varchar] (80) NULL ,
[Bezeichnung5] [varchar] (80) NULL ,
[BeschreibungLang2] [text] NULL ,
[BeschreibungLang3] [text] NULL ,
[BeschreibungLang4] [text] NULL ,
[BeschreibungLang5] [text] NULL ,
[anlage_datum] [datetime] NULL ,
[anlage_zeichen] [char] (16) NULL ,
[aender_datum] [datetime] NULL ,
[aender_zeichen] [char] (16) NULL ,
[ArtikelNrLief1] [varchar] (32) NULL ,
[Lieferant1] [varchar] (8) NULL ,
[ArtikelNrLief2] [varchar] (32) NULL ,
[Lieferant2] [varchar] (8) NULL ,
[ArtikelNrLief3] [varchar] (32) NULL ,
[Lieferant3] [varchar] (8) NULL ,
[Freigabe1] [tinyint] NULL ,
[Freigabe2] [tinyint] NULL ,
[Freigabe3] [tinyint] NULL ,
[Tag1] [varchar] (16) NULL ,
[Tag2] [varchar] (16) NULL
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
CREATE INDEX [ArtikelNr] ON [dbo].[Artikel]([ArtikelNr]) WITH FILLFACTOR
= 90 ON [PRIMARY]
CREATE INDEX [VariationsAttribut] ON [dbo].[Artikel]([VariationsAttribut])
WITH FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [AttributGruppenId] ON [dbo].[Artikel]([AttributGruppenId])
WITH FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [ArtikelNrLief1] ON [dbo].[Artikel]([ArtikelNrLief1]) WITH
FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [ArtikelNrLief2] ON [dbo].[Artikel]([ArtikelNrLief2]) WITH
FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [ArtikelNrLief3] ON [dbo].[Artikel]([ArtikelNrLief3]) WITH
FILLFACTOR = 90 ON [PRIMARY]
=== Aufbau Tabelle AG======== CREATE TABLE [dbo].[AttributGruppen] (
[GuidID] [char] (32) NOT NULL ,
[Reihenfolge] [int] NULL ,
[Ebene] [int] NULL ,
[Bezeichnung1] [varchar] (1024) NULL ,
[Bezeichnung2] [varchar] (1024) NULL ,
[Bezeichnung3] [varchar] (1024) NULL ,
[Bezeichnung4] [varchar] (1024) NULL ,
[Bezeichnung5] [varchar] (1024) NULL ,
[anlage_datum] [datetime] NULL ,
[anlage_zeichen] [char] (16) NULL ,
[aender_datum] [datetime] NULL ,
[aender_zeichen] [char] (16) NULL ,
[AttributGruppenNummer] [varchar] (15) NULL
) ON [PRIMARY]
CREATE INDEX [Ebene] ON [dbo].[AttributGruppen]([Ebene]) WITH FILLFACTOR
= 90 ON [PRIMARY]
=== Aufbau Tabelle SA======== CREATE TABLE [dbo].[StrukturArtikel] (
[StrukturID] [char] (32) NOT NULL ,
[StrukturKatalogID] [char] (32) NOT NULL ,
[ArtikelID] [char] (32) NOT NULL ,
[Katalogspezifisch] [bit] NULL ,
[Reihenfolge] [int] NULL ,
[Parent] [char] (32) NULL ,
[Ebene] [int] NULL ,
[anlage_datum] [datetime] NULL ,
[anlage_zeichen] [char] (16) NULL ,
[aender_datum] [datetime] NULL ,
[aender_zeichen] [char] (16) NULL
) ON [PRIMARY]
CREATE INDEX [ArtikelID] ON [dbo].[StrukturArtikel]([ArtikelID]) WITH
FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [Parent] ON [dbo].[StrukturArtikel]([Parent]) WITH
FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [StrukturID] ON [dbo].[StrukturArtikel]([StrukturID]) WITH
FILLFACTOR = 90 ON [PRIMARY]
CREATE INDEX [StrukturKatalogID] ON
[dbo].[StrukturArtikel]([StrukturKatalogID]) WITH FILLFACTOR = 90 ON
[PRIMARY]Did you update stats after copying everything over? When
you say new application, you mean it was only converted
for SQL2K? or are there logic changes also? Compare
that all indexing is carried over, if it was supposed to
be!?! Beyond that, give SQL Profiler a shot to see the
exact slow statements and take it from there... Bruce
>--Original Message--
>Hi,
>I took a copy of a SQL7-Database with DTS to an SQL2000
Server.
>The new copy of the SQL2000 runns fine. Also the
application useing the new
>DB.
>But some of the SQL Commands became very solw (<1s =>
>200s).
>Is it neceserry to optimize all the SQL-Commands - what
e horror.
>Thanks a lot
>Andreas
>
>Here the commands and the tabledef:
>SELECT AG.GuidID, AG.Bezeichnung1 FROM
>(Artikel A INNER JOIN StrukturArtikel SA ON A.GuidID =SA.ArtikelID)
>INNER JOIN Attributgruppen AG ON A.AttributGruppenID =AG.GuidID
>GROUP BY AG.GuidID, AG.Bezeichnung1, SA.StrukturKatalogID
>HAVING SA.StrukturKatalogID
= '5269C032AB1011D787D20000CB531E4D' ORDER BY
>AG.Bezeichnung1
>
>=== Aufbau Tabelle A========>CREATE TABLE [dbo].[Artikel] (
> [GuidID] [char] (32) NOT NULL ,
> [ArtikelNr] [varchar] (32) NULL ,
> [AttributGruppenId] [char] (32) NULL ,
> [VariationsAttribut] [char] (32) NULL ,
> [Varianz] [varchar] (50) NULL ,
> [Bezeichnung1] [varchar] (80) NULL ,
> [BeschreibungLang1] [text] NULL ,
> [VariationsBlockID] [char] (32) NULL ,
> [Bezeichnung2] [varchar] (80) NULL ,
> [Bezeichnung3] [varchar] (80) NULL ,
> [Bezeichnung4] [varchar] (80) NULL ,
> [Bezeichnung5] [varchar] (80) NULL ,
> [BeschreibungLang2] [text] NULL ,
> [BeschreibungLang3] [text] NULL ,
> [BeschreibungLang4] [text] NULL ,
> [BeschreibungLang5] [text] NULL ,
> [anlage_datum] [datetime] NULL ,
> [anlage_zeichen] [char] (16) NULL ,
> [aender_datum] [datetime] NULL ,
> [aender_zeichen] [char] (16) NULL ,
> [ArtikelNrLief1] [varchar] (32) NULL ,
> [Lieferant1] [varchar] (8) NULL ,
> [ArtikelNrLief2] [varchar] (32) NULL ,
> [Lieferant2] [varchar] (8) NULL ,
> [ArtikelNrLief3] [varchar] (32) NULL ,
> [Lieferant3] [varchar] (8) NULL ,
> [Freigabe1] [tinyint] NULL ,
> [Freigabe2] [tinyint] NULL ,
> [Freigabe3] [tinyint] NULL ,
> [Tag1] [varchar] (16) NULL ,
> [Tag2] [varchar] (16) NULL
>) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
> CREATE INDEX [ArtikelNr] ON [dbo].[Artikel]
([ArtikelNr]) WITH FILLFACTOR
>= 90 ON [PRIMARY]
> CREATE INDEX [VariationsAttribut] ON [dbo].[Artikel]
([VariationsAttribut])
>WITH FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [AttributGruppenId] ON [dbo].[Artikel]
([AttributGruppenId])
>WITH FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [ArtikelNrLief1] ON [dbo].[Artikel]
([ArtikelNrLief1]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [ArtikelNrLief2] ON [dbo].[Artikel]
([ArtikelNrLief2]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [ArtikelNrLief3] ON [dbo].[Artikel]
([ArtikelNrLief3]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
>
>=== Aufbau Tabelle AG========>CREATE TABLE [dbo].[AttributGruppen] (
> [GuidID] [char] (32) NOT NULL ,
> [Reihenfolge] [int] NULL ,
> [Ebene] [int] NULL ,
> [Bezeichnung1] [varchar] (1024) NULL ,
> [Bezeichnung2] [varchar] (1024) NULL ,
> [Bezeichnung3] [varchar] (1024) NULL ,
> [Bezeichnung4] [varchar] (1024) NULL ,
> [Bezeichnung5] [varchar] (1024) NULL ,
> [anlage_datum] [datetime] NULL ,
> [anlage_zeichen] [char] (16) NULL ,
> [aender_datum] [datetime] NULL ,
> [aender_zeichen] [char] (16) NULL ,
> [AttributGruppenNummer] [varchar] (15) NULL
>) ON [PRIMARY]
> CREATE INDEX [Ebene] ON [dbo].[AttributGruppen]
([Ebene]) WITH FILLFACTOR
>= 90 ON [PRIMARY]
>
>=== Aufbau Tabelle SA========>CREATE TABLE [dbo].[StrukturArtikel] (
> [StrukturID] [char] (32) NOT NULL ,
> [StrukturKatalogID] [char] (32) NOT NULL ,
> [ArtikelID] [char] (32) NOT NULL ,
> [Katalogspezifisch] [bit] NULL ,
> [Reihenfolge] [int] NULL ,
> [Parent] [char] (32) NULL ,
> [Ebene] [int] NULL ,
> [anlage_datum] [datetime] NULL ,
> [anlage_zeichen] [char] (16) NULL ,
> [aender_datum] [datetime] NULL ,
> [aender_zeichen] [char] (16) NULL
>) ON [PRIMARY]
> CREATE INDEX [ArtikelID] ON [dbo].[StrukturArtikel]
([ArtikelID]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [Parent] ON [dbo].[StrukturArtikel]
([Parent]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [StrukturID] ON [dbo].[StrukturArtikel]
([StrukturID]) WITH
>FILLFACTOR = 90 ON [PRIMARY]
> CREATE INDEX [StrukturKatalogID] ON
>[dbo].[StrukturArtikel]([StrukturKatalogID]) WITH
FILLFACTOR = 90 ON
>[PRIMARY]
>
>.
>
Subscribe to:
Posts (Atom)