What is the minimum requirement or version of Visual Studio.NET
necessary for editing reports when running Reporting Services. I am
running on a SQL 2000 sp3 and Windows 2003 server.Anything that comes with VS.2003 (It cannot be VS 2005). The cheapest is
VB.Net
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"refdk" <fuhlendorf@.gmail.com> wrote in message
news:1140804364.362272.141300@.z34g2000cwc.googlegroups.com...
> What is the minimum requirement or version of Visual Studio.NET
> necessary for editing reports when running Reporting Services. I am
> running on a SQL 2000 sp3 and Windows 2003 server.
>|||Thanks, I will try that :-)
/Ren=E9
Showing posts with label requirement. Show all posts
Showing posts with label requirement. Show all posts
Friday, March 23, 2012
Minimum RAM Requirement For installation
256 RAM is running on my computer. is it possible to run Microsoft SQL Server 2005 Reporting Services on it?
NOTE: I installed Microsoft SQL Server 2005 Reporting Services. By the installation, it gives an error, that system resource is not enough. Although this, installation resume, but program not worked at the end.
I
No.
http://www.microsoft.com/downloads/details.aspx?familyid=1E53F882-0C16-4847-B331-132274AE8C84&displaylang=en#Requirements
Wednesday, March 21, 2012
Minimum Hardware Requirement Warning
Hi all, we have released a shrink-wrapped software package that uses SQL Server Express as it's backend. I am currently tracking down an issue to do with SQL Server Express not installing correctly, and at the end of a lot of investigation I have come to the conclusion that it is a CPU problem.
The CPU is not "PII Compatible" enough for SQL Express. It appears as though the Cache prefetching instructions are the most likely culprit, but I was just wondering why the SQL Server Installer allows the user to continue with only a warning about the minimum hardware requirement not being met?
It seems to me that a lot of time and pain would be saved if the installer just said "Sorry, but you have no hope in hell of running SQL Server... go out and buy yourself a real machine" instead of allowing the user to continue all the way through the install and finally crash out at the final step.
Hey Scott,
Yeah, it turns out that the cache prefetching is required and we're not checking for it up front. I've filed a request to add that check for the next version of the product.
-Jeffrey.
|||Thanks, that would be a great help.|||Sorry, signed in with the wrong passport.
This will be a great help, thanks.
Minimum client connectivity requirement
I have Win9x clients. For them to be able to write to a
SQL database (2000), I think I would need to install
MDAC. However, many of these clients are connected with
an extremely slow WAN connection (56K) which makes MDAC
install via login script difficult or impossible. I don't
need the connectivity to all the other DB systems that
MDAC includes. Can I break it up to only install the
necessary components for TCP/IP and Named Pipes
connectivity to SQL server? If so, how can I find out
what files I need, and what if any registry entries need
to be made?
Thanks!
Installing MDAC 2.6 would be the basic requirement.
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:1ce701c42706$37dc7ba0$a001280a@.phx.gbl...
> I have Win9x clients. For them to be able to write to a
> SQL database (2000), I think I would need to install
> MDAC. However, many of these clients are connected with
> an extremely slow WAN connection (56K) which makes MDAC
> install via login script difficult or impossible. I don't
> need the connectivity to all the other DB systems that
> MDAC includes. Can I break it up to only install the
> necessary components for TCP/IP and Named Pipes
> connectivity to SQL server? If so, how can I find out
> what files I need, and what if any registry entries need
> to be made?
> Thanks!
|||This is correct. There is no piecmeal approach to installing the
connectivity components to connect to SQL Server 2000.
Rand
This posting is provided "as is" with no warranties and confers no rights.
SQL database (2000), I think I would need to install
MDAC. However, many of these clients are connected with
an extremely slow WAN connection (56K) which makes MDAC
install via login script difficult or impossible. I don't
need the connectivity to all the other DB systems that
MDAC includes. Can I break it up to only install the
necessary components for TCP/IP and Named Pipes
connectivity to SQL server? If so, how can I find out
what files I need, and what if any registry entries need
to be made?
Thanks!
Installing MDAC 2.6 would be the basic requirement.
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:1ce701c42706$37dc7ba0$a001280a@.phx.gbl...
> I have Win9x clients. For them to be able to write to a
> SQL database (2000), I think I would need to install
> MDAC. However, many of these clients are connected with
> an extremely slow WAN connection (56K) which makes MDAC
> install via login script difficult or impossible. I don't
> need the connectivity to all the other DB systems that
> MDAC includes. Can I break it up to only install the
> necessary components for TCP/IP and Named Pipes
> connectivity to SQL server? If so, how can I find out
> what files I need, and what if any registry entries need
> to be made?
> Thanks!
|||This is correct. There is no piecmeal approach to installing the
connectivity components to connect to SQL Server 2000.
Rand
This posting is provided "as is" with no warranties and confers no rights.
minimal hardware requirement for SQL failover clustering
HI,
I would like to build a SQL 2000 failover clustering to improve my network
knowledge. For testing and learning purpose, what's the minimal hareware
requirment?
Best Regards,
Lynn
Hi
Hardware should be from the the Microsoft HCL
But typically:
2 Identical Servers with Minimum 512Mb RAM
4 NICs
1 x SAN
2 x SAN connectivity
Network and other cabling
Or as Uttam answered yesterday:
"
Lynn,
For testing purposes, you may find this useful
Using Microsoft Virtual Server 2005 to Create and Configure a Two-Node
Microsoft Windows Server 2003 Cluster
This guide provides step-by-step instructions for using Virtual Server 2005
to create and configure a two-node server cluster.
http://www.microsoft.com/technet/pro...y/cvs2005.mspx
If you do not want to install virtual server and want to build using minimum
hardware, long ago I had build a two node cluster using two laptops
with
SCSI card and one
SCSI disk and a cross-over cable. This is the bare minimum. I also was able
to install SQL Server 2000 clustered instance on this bare min cluster. It
worked and was good
for testing but NOT supported and also it did not work sometimes as
expected. Ofcourse, I would not do this for a real test cluster or dev
cluster.
Best Regards,
Uttam Parui
Microsoft Corporation
"
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:4B93ABB7-5F40-478D-B4E9-009520E72C94@.microsoft.com...
> HI,
> I would like to build a SQL 2000 failover clustering to improve my network
> knowledge. For testing and learning purpose, what's the minimal hareware
> requirment?
> --
> Best Regards,
> Lynn
|||Mike,
Thank you so much for your quick response. It's very useful.
Rihgt now, I already have a machine with 512 RAM, and I would like buy a new
machine with higher hardware component. Is "two identical machines" the
must-be? Or, I can configure two-node failover clustering with two different
hardware component machines.
Best Regards,
Lynn
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Hardware should be from the the Microsoft HCL
> But typically:
> 2 Identical Servers with Minimum 512Mb RAM
> 4 NICs
> 1 x SAN
> 2 x SAN connectivity
> Network and other cabling
> Or as Uttam answered yesterday:
> "
> Lynn,
> For testing purposes, you may find this useful
> Using Microsoft Virtual Server 2005 to Create and Configure a Two-Node
> Microsoft Windows Server 2003 Cluster
> This guide provides step-by-step instructions for using Virtual Server 2005
> to create and configure a two-node server cluster.
> http://www.microsoft.com/technet/pro...y/cvs2005.mspx
> If you do not want to install virtual server and want to build using minimum
> hardware, long ago I had build a two node cluster using two laptops with
> SCSI card and one
> SCSI disk and a cross-over cable. This is the bare minimum. I also was able
> to install SQL Server 2000 clustered instance on this bare min cluster. It
> worked and was good
> for testing but NOT supported and also it did not work sometimes as
> expected. Ofcourse, I would not do this for a real test cluster or dev
> cluster.
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> "
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:4B93ABB7-5F40-478D-B4E9-009520E72C94@.microsoft.com...
>
>
|||Are you looking to build a Highly Available 2-node cluster that is fully supported by Microsoft and the hardware vendor? Or are you just looking to build a 2-node cluster
for testing?
Yesterday, I had already answered for the latter.
For the former -- i.e. to build a highly available cluster supported by Microsoft and hardware vendor, you need a "Qualified complete cluster solution". So, where does
one find the list of complete cluster solutions that are qualified?
The most current Cluster Hardware Compatibility List (HCL) is available at the following Microsoft Web site:
http://www.microsoft.com/hcl (http://www.microsoft.com/hcl)
When you visit this site, click the Cluster category. The Cluster and Cluster/Datacenter categories display only complete cluster solutions that have been qualified. The
subcategories list components that have passed Cluster Component Candidate testing. These cluster components are listed for Original Equipment Manufacturers
(OEMs) and System Integrators to design complete clusters and then submit a complete cluster solution for testing.
The most current Cluster Windows Server Catalog (WSC) is available at the following Microsoft Web Site:
http://www.microsoft.com/windows/catalog/server/ (http://www.microsoft.com/windows/catalog/server/)
When you visit this site, click the Hardware tab, and then click on the Cluster Solutions category. The Cluster Solutions category displays only complete cluster solutions
that have been qualified.
NOTE:
Customers should not use this list to build a cluster solution because using these individual components in a cluster does not qualify as a complete HCL or WSC
solution. Microsoft fully supports only clusters that are complete solutions that are listed in the Cluster category on the HCL or WSC.
To answer you qs "Is "two identical machines" the must-be? Or, I can configure two-node failover clustering with two different hardware component machines."
ANS. Currently today, a vendor can submit a solution for testing / qualification if the hardware is dissimilar. For example a Proliant DL380 as one node and a Proliant
DL580 as another node. But the ENTIRE SOLUTION still needs to be submitted as a COMPLETE SOLUTION and Windows Hardware Quality Labs (WHQL) qualified.
Now it is true that these are rare...
Recommended Reading
======================
The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog
http://support.microsoft.com/default...b;en-us;309395
The Microsoft support policy for a SQL Server failover cluster
http://support.microsoft.com/default...b;en-us;327518
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest
way to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
I would like to build a SQL 2000 failover clustering to improve my network
knowledge. For testing and learning purpose, what's the minimal hareware
requirment?
Best Regards,
Lynn
Hi
Hardware should be from the the Microsoft HCL
But typically:
2 Identical Servers with Minimum 512Mb RAM
4 NICs
1 x SAN
2 x SAN connectivity
Network and other cabling
Or as Uttam answered yesterday:
"
Lynn,
For testing purposes, you may find this useful
Using Microsoft Virtual Server 2005 to Create and Configure a Two-Node
Microsoft Windows Server 2003 Cluster
This guide provides step-by-step instructions for using Virtual Server 2005
to create and configure a two-node server cluster.
http://www.microsoft.com/technet/pro...y/cvs2005.mspx
If you do not want to install virtual server and want to build using minimum
hardware, long ago I had build a two node cluster using two laptops
withSCSI card and one
SCSI disk and a cross-over cable. This is the bare minimum. I also was able
to install SQL Server 2000 clustered instance on this bare min cluster. It
worked and was good
for testing but NOT supported and also it did not work sometimes as
expected. Ofcourse, I would not do this for a real test cluster or dev
cluster.
Best Regards,
Uttam Parui
Microsoft Corporation
"
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:4B93ABB7-5F40-478D-B4E9-009520E72C94@.microsoft.com...
> HI,
> I would like to build a SQL 2000 failover clustering to improve my network
> knowledge. For testing and learning purpose, what's the minimal hareware
> requirment?
> --
> Best Regards,
> Lynn
|||Mike,
Thank you so much for your quick response. It's very useful.
Rihgt now, I already have a machine with 512 RAM, and I would like buy a new
machine with higher hardware component. Is "two identical machines" the
must-be? Or, I can configure two-node failover clustering with two different
hardware component machines.
Best Regards,
Lynn
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Hardware should be from the the Microsoft HCL
> But typically:
> 2 Identical Servers with Minimum 512Mb RAM
> 4 NICs
> 1 x SAN
> 2 x SAN connectivity
> Network and other cabling
> Or as Uttam answered yesterday:
> "
> Lynn,
> For testing purposes, you may find this useful
> Using Microsoft Virtual Server 2005 to Create and Configure a Two-Node
> Microsoft Windows Server 2003 Cluster
> This guide provides step-by-step instructions for using Virtual Server 2005
> to create and configure a two-node server cluster.
> http://www.microsoft.com/technet/pro...y/cvs2005.mspx
> If you do not want to install virtual server and want to build using minimum
> hardware, long ago I had build a two node cluster using two laptops
with> SCSI card and one
> SCSI disk and a cross-over cable. This is the bare minimum. I also was able
> to install SQL Server 2000 clustered instance on this bare min cluster. It
> worked and was good
> for testing but NOT supported and also it did not work sometimes as
> expected. Ofcourse, I would not do this for a real test cluster or dev
> cluster.
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> "
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:4B93ABB7-5F40-478D-B4E9-009520E72C94@.microsoft.com...
>
>
|||Are you looking to build a Highly Available 2-node cluster that is fully supported by Microsoft and the hardware vendor? Or are you just looking to build a 2-node cluster
for testing?
Yesterday, I had already answered for the latter.
For the former -- i.e. to build a highly available cluster supported by Microsoft and hardware vendor, you need a "Qualified complete cluster solution". So, where does
one find the list of complete cluster solutions that are qualified?
The most current Cluster Hardware Compatibility List (HCL) is available at the following Microsoft Web site:
http://www.microsoft.com/hcl (http://www.microsoft.com/hcl)
When you visit this site, click the Cluster category. The Cluster and Cluster/Datacenter categories display only complete cluster solutions that have been qualified. The
subcategories list components that have passed Cluster Component Candidate testing. These cluster components are listed for Original Equipment Manufacturers
(OEMs) and System Integrators to design complete clusters and then submit a complete cluster solution for testing.
The most current Cluster Windows Server Catalog (WSC) is available at the following Microsoft Web Site:
http://www.microsoft.com/windows/catalog/server/ (http://www.microsoft.com/windows/catalog/server/)
When you visit this site, click the Hardware tab, and then click on the Cluster Solutions category. The Cluster Solutions category displays only complete cluster solutions
that have been qualified.
NOTE:
Customers should not use this list to build a cluster solution because using these individual components in a cluster does not qualify as a complete HCL or WSC
solution. Microsoft fully supports only clusters that are complete solutions that are listed in the Cluster category on the HCL or WSC.
To answer you qs "Is "two identical machines" the must-be? Or, I can configure two-node failover clustering with two different hardware component machines."
ANS. Currently today, a vendor can submit a solution for testing / qualification if the hardware is dissimilar. For example a Proliant DL380 as one node and a Proliant
DL580 as another node. But the ENTIRE SOLUTION still needs to be submitted as a COMPLETE SOLUTION and Windows Hardware Quality Labs (WHQL) qualified.
Now it is true that these are rare...
Recommended Reading
======================
The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog
http://support.microsoft.com/default...b;en-us;309395
The Microsoft support policy for a SQL Server failover cluster
http://support.microsoft.com/default...b;en-us;327518
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest
way to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
Monday, February 20, 2012
Migrating Systems
I am to be involved in moving 3 clusters soon from one data center in the
Northeast to Texas. The main requirement is to have the shortest cutover
period possible via some kind of replicated technologies.
System 1 - 64-bit SQL Server 2000 SP4 to a like environment. I see no
issue with that one. Stage the new server, restore a backup and put it in
log shipping or use a product like Double-Take to keep things in sync.
System 2 - 32-bit SQL Server 2000 SP3a to 64-bit SQL Server 2000 SP4. This
instance has over 200 databases on it. Don't think log shipping is an
option here. It's not indexed well enough for replication and because the
environments aren't like I don't think Double-Take will work. Ideas?
System 3 - 32-bit SQL Server 7 SP4 to a 64-bit SQL Server 2000 SP4. The SQL
7 cluster is currently on Windows NT. Same scenario as System 2.
Ideas?
I think the fastest way to do this is to migrate all dependencies and
accounts, and then detach and reattach the databases on the new server. Copy
the database don't move them.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Cathy Soloway" <CathySoloway@.discussions.microsoft.com> wrote in message
news:8C4A9E42-D424-4DF9-A5ED-1C3821F2E033@.microsoft.com...
>I am to be involved in moving 3 clusters soon from one data center in the
> Northeast to Texas. The main requirement is to have the shortest cutover
> period possible via some kind of replicated technologies.
> System 1 - 64-bit SQL Server 2000 SP4 to a like environment. I see no
> issue with that one. Stage the new server, restore a backup and put it in
> log shipping or use a product like Double-Take to keep things in sync.
> System 2 - 32-bit SQL Server 2000 SP3a to 64-bit SQL Server 2000 SP4.
> This
> instance has over 200 databases on it. Don't think log shipping is an
> option here. It's not indexed well enough for replication and because the
> environments aren't like I don't think Double-Take will work. Ideas?
> System 3 - 32-bit SQL Server 7 SP4 to a 64-bit SQL Server 2000 SP4. The
> SQL
> 7 cluster is currently on Windows NT. Same scenario as System 2.
> Ideas?
>
Northeast to Texas. The main requirement is to have the shortest cutover
period possible via some kind of replicated technologies.
System 1 - 64-bit SQL Server 2000 SP4 to a like environment. I see no
issue with that one. Stage the new server, restore a backup and put it in
log shipping or use a product like Double-Take to keep things in sync.
System 2 - 32-bit SQL Server 2000 SP3a to 64-bit SQL Server 2000 SP4. This
instance has over 200 databases on it. Don't think log shipping is an
option here. It's not indexed well enough for replication and because the
environments aren't like I don't think Double-Take will work. Ideas?
System 3 - 32-bit SQL Server 7 SP4 to a 64-bit SQL Server 2000 SP4. The SQL
7 cluster is currently on Windows NT. Same scenario as System 2.
Ideas?
I think the fastest way to do this is to migrate all dependencies and
accounts, and then detach and reattach the databases on the new server. Copy
the database don't move them.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Cathy Soloway" <CathySoloway@.discussions.microsoft.com> wrote in message
news:8C4A9E42-D424-4DF9-A5ED-1C3821F2E033@.microsoft.com...
>I am to be involved in moving 3 clusters soon from one data center in the
> Northeast to Texas. The main requirement is to have the shortest cutover
> period possible via some kind of replicated technologies.
> System 1 - 64-bit SQL Server 2000 SP4 to a like environment. I see no
> issue with that one. Stage the new server, restore a backup and put it in
> log shipping or use a product like Double-Take to keep things in sync.
> System 2 - 32-bit SQL Server 2000 SP3a to 64-bit SQL Server 2000 SP4.
> This
> instance has over 200 databases on it. Don't think log shipping is an
> option here. It's not indexed well enough for replication and because the
> environments aren't like I don't think Double-Take will work. Ideas?
> System 3 - 32-bit SQL Server 7 SP4 to a 64-bit SQL Server 2000 SP4. The
> SQL
> 7 cluster is currently on Windows NT. Same scenario as System 2.
> Ideas?
>
Subscribe to:
Posts (Atom)