Microsoft SQL Server client license costs

I have three questions: Could anyone help.
1. How much does a Microsoft SQL Server client license cost?
2. If we have web interface as the front end and SQL server as the back end,
do we need client licenses for those accessing their databases via the web?
3. Also if we have people accessing the server with Access,do we need
licenses for those?
"bgm" <bgm@.discussions.microsoft.com> wrote in message
news:17913AFE-A04D-47B3-96A7-C4216A68E6D8@.microsoft.com...
> I have three questions: Could anyone help.
> 1. How much does a Microsoft SQL Server client license cost?
http://www.microsoft.com/sql/howtobuy/default.asp

> 2. If we have web interface as the front end and SQL server as the back
end,
> do we need client licenses for those accessing their databases via the
web?
It's better to buy a per-processor licence because you do not know the
number of users (or you have developed a database access componenet and you
need to limit the number of concurrent users).

> 3. Also if we have people accessing the server with Access,do we need
> licenses for those?
It's an extra connection.
|||>> 2. If we have web interface as the front end and SQL server as the back
> end,
> web?
> It's better to buy a per-processor licence because you do not know the
> number of users (or you have developed a database access componenet and
> you
> need to limit the number of concurrent users).
the only option is per processor license! You can't use per user connection
license.

Microsoft SQL Server client license costs

I have three questions here:Could anyone help.
1.How much does a Microsoft SQL Server client license cost?
2.If we have web interface as the front end and SQL server as the back
end,do we need client licenses for those accessing the databases via the web?
3.If we have people accessing the server with Access,do we need licenses for
those?
Hi,
You can check the following whitepaper and article for information on SQL
Server licensing and prices
http://www.microsoft.com/sql/howtobu...licensing.asp.
http://www.microsoft.com/sql/howtobuy/faq.asp
You can also call (800) 426-9400 to clarify your doubts on the licensing.
Regards,
Gayathri Rau [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
sql

Microsoft SQL Server Certifications

Hello all,

I'm working as DBA.I wish to do certifications for Microsoft sql server.So Could i know what are the certifications are available and what i've to do for certififcations.

Thanks in advance
David RPlease find all the details here.

Microsoft SQL Server Best Practices Analyzer

Should this tool be installed and run in a production server?
MM
barney@.newsgroups.nospam
Martin,
If you are concerned about installing this tool on production server, you
can install this tool on a remote machine and you could analyze a production
server from a remote machine (as long as you can connect to target SQL
Server from remote machine)
SQL Best Practices Analyzer relies on the BPA Repository database, which is
a SQL Server database created during SQL BPA installation. You can have this
BPA repository database created on local SQL Server or a remote SQL Server.
SQL Best Practices Analyzer requires the following components to be
installed on the machine
.. Microsoft Internet Explorer 6.0 or later
.. Microsoft .Net Framework 1.1
Reference:
http://www.microsoft.com/downloads/d...displaylang=en
Thanks
Sethu
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
"Martin Millar" <barney@.newsgroups.nospam> wrote in message
news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
> Should this tool be installed and run in a production server?
> --
> MM
> barney@.newsgroups.nospam
|||Thanks for this. perhaps I should have been a bit more precise. I am a
developer and I'm having a beef with my DBA who has installed this on the
live production server. My argument is that this should be installed and run
on a test system as there is no need to test the performance of the hardware
on which the DB runs on.
If it's OK on Test then it gets ported to live. I believe that anything that
does not need to be installed on a production server should not be on there
as there is a danger that something else running on the box may result in a
loss of service or may intoduce a risk of virus or attack. This tool requires
the dot.net framework and I am a strong fan of this being an asp.net
developer. But until this (dot.net) becomes a core part of the OS (i.e. when
it's installed by default on XP, win2003 etc) I categorise this as a
development add-on and has an attached if installed.
If MS release a security patch for dot.net then I need to schedule downtime
on the production server to apply this.
So back to my original question, which is in itself is about best practises,
should it be best practise to install the BPA on a production server?
Thanks in advance
"Sethu Srinivasan [MSFT]" wrote:

> Martin,
> If you are concerned about installing this tool on production server, you
> can install this tool on a remote machine and you could analyze a production
> server from a remote machine (as long as you can connect to target SQL
> Server from remote machine)
> SQL Best Practices Analyzer relies on the BPA Repository database, which is
> a SQL Server database created during SQL BPA installation. You can have this
> BPA repository database created on local SQL Server or a remote SQL Server.
> SQL Best Practices Analyzer requires the following components to be
> installed on the machine
> .. Microsoft Internet Explorer 6.0 or later
> .. Microsoft .Net Framework 1.1
> Reference:
> http://www.microsoft.com/downloads/d...displaylang=en
>
> Thanks
> Sethu
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm.
>
> "Martin Millar" <barney@.newsgroups.nospam> wrote in message
> news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
>
>

Microsoft SQL Server and Other DBMS

Hello:

Many companies use DBMS that are not Microsoft SQL Server. Those companies use Oracle, PostgreSQL, MySQL and Ingres, for example. I'm looking for a paper o website which exponses the advantages (strengths) and disadvantages (weakness) of those DBMS. Why? Our customers would like a comparison between different systems, and we must show them the Microsoft SQL Server possibilities.

Can you help me with this? In terms of performance, speed, security, maintenance, etc.

Thanks.

We offer comparison information for SQL Server at http://www.microsoft.com/sql/prodinfo/compare/default.mspx, this information should help you start filling out the information you need to compare the different RDBMS systems out there.

Mike

Microsoft SQL Server and Other DBMS

Hello:

Many companies use DBMS that are not Microsoft SQL Server. Those companies use Oracle, PostgreSQL, MySQL and Ingres, for example. I'm looking for a paper o website which exponses the advantages (strengths) and disadvantages (weakness) of those DBMS. Why? Our customers would like a comparison between different systems, and we must show them the Microsoft SQL Server possibilities.

Can you help me with this? In terms of performance, speed, security, maintenance, etc.

Thanks.

We offer comparison information for SQL Server at http://www.microsoft.com/sql/prodinfo/compare/default.mspx, this information should help you start filling out the information you need to compare the different RDBMS systems out there.

Mike

Microsoft SQL server 6.5 to 2005

Hi Fellas,
I would really appreciate if you could help me out with the following two questions?
1) Can 2005 server files be converted to 6.5? and how?
2) How easy it to upgrade from 6.5 to 2005? and how?
I would be really grateful by your help
NickNot so easy task to do as you have to compare each and every aspect of the database to ensure they work in compatibility of SQL 2005.

Refer to http://sqlserver-qa.net/blogs/tools/archive/2007/04/12/set-a-stage-for-smooth-upgrades-of-your-sql-server-environment.aspx & http://sqlserver-qa.net/blogs/tools/pages/easy-way-to-upgrade-from-previous-version-of-sql-server.aspx in this case.|||Thanks a lot, i appreciate.|||Maverick

I should imagine it would depend on the size & complexity of the 6.5 DB

For a simple DB I would probably just script out the Schema then, run script & right click - import the data on the 2005 box then - suck it & see fixing any issues (IF there are any) in testing.

Or you could spend your life reading up on the possible failures & effects that may occur as Satya suggests

GWsql

Microsoft SQL server 2005, connection string

<

connectionStrings>

<

addname="AppConnectionString1"connectionString="Data Source=".\SQLEXPRESS";AttachDbFilename="C:\Program Files\Microsoft SQL Server\MSSQL\Data\AdventureWorks2000_Data.mdf";Integrated Security=True"providerName="System.Data.SqlClient" />

</

connectionStrings>

I'm running Microsoft SQL server 2005. what is the error in the above code.

What is the error that you are getting?|||

a database not found error message.

here's some background:

I've followed the instructions here :http://msdn2.microsoft.com/library/ms310325.aspx as before, and everything went well till.

"To configure AdventureWorks to work with Web server controls"

sqlcmd -E -S (local)\sqlexpress -Q "sp_grantlogin N'NT AUTHORITY\NETWORK SERVICE'"

My machine name is Leigh, i run win xp home edition, and MS SQL server 2005, so the above command in my case should be :

sqlcmd -E -S (local)\sqlexpress -Q "sp_grantlogin N' Leigh\ASPNET'" ? (which doesn't work i assume because not happens )

Microsoft SQL Server 2005 SP2 Issue

An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services should be aware of a change in SP2 that affects existing cleanup
tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, those plans include a History Cleanup
Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.
*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services should be aware of a change in SP2 that affects existing cleanup
> tasks until updated using SQL Server SP2 tools.
> Who is affected?
> You are affected if you use cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, those plans include a History
> Cleanup
> Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
> Users of SQL Server 2000 legacy maintenance plans are not affected.
> What is the issue?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>

Microsoft SQL Server 2005 SP2 Issue

An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services should be aware of a change in SP2 that affects existing cleanup
tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, those plans include a History Cleanup
Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.
*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:OGpfQVFYHHA.4368@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services should be aware of a change in SP2 that affects existing cleanup
> tasks until updated using SQL Server SP2 tools.
> Who is affected?
> You are affected if you use cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, those plans include a History
> Cleanup
> Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
> Users of SQL Server 2000 legacy maintenance plans are not affected.
> What is the issue?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>

Microsoft SQL Server 2005 SP2 Issue

An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services should be aware of a change in SP2 that affects existing cleanup
tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, those plans include a History Cleanup
Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services should be aware of a change in SP2 that affects existing cleanup
> tasks until updated using SQL Server SP2 tools.
> Who is affected?
> You are affected if you use cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, those plans include a History
> Cleanup
> Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
> Users of SQL Server 2000 legacy maintenance plans are not affected.
> What is the issue?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>

Microsoft SQL Server 2005 SP2 Issue

An issue was recently discovered with SQL Server 2005 SP2 which might impact
customers using cleanup tasks in Maintenance Plans and SQL Server
Integration Services packages. The issue is described in detail at
http://support.microsoft.com/kb/933508. We have created a General
Distribution Release (GDR) #50000939 to address this issue which is
available for download and we have included the GDR in a refresh of the SP2
installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to
need any further action since the refreshed SP2 installation package
includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to
March 5th, 2007 apply the GDR either from Microsoft Update or by downloading
it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described
in the KB article (http://support.microsoft.com/kb/933508), this is
primarily for customers who use cleanup tasks in maintenance plans and SQL
Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration
Services should be aware of a change in SP2 that affects existing cleanup
tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL
Server Integration Services packages, those plans include a History Cleanup
Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days,
weeks, months, or years. In response to customer feedback, SQL Server 2005
SP2 includes significant enhancements to maintenance plans. These include an
enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to
misinterpret existing cleanup task intervals in maintenance plans and
Integration Services packages. This can lead to the files being cleaned up
earlier than intended. The issue is described in detail at
http://support.microsoft.com/kb/933508.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
install a general distribution release (GDR) update for those SQL Server
2005 SP2 installations. The GDR is available from the Microsoft Download
Center at http://go.microsoft.com/fwlink/?LinkId=85124
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied
automatically if you are using automatic updates. However, if you are using
failover clustering, you must download and apply the GDR manually. Microsoft
Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the
current SQL Server 2005 SP2 download is updated to resolve this issue. If
you have not installed the initial release of SP2, you can download the
current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation,
no files are updated. Instead, use the general distribution release (GDR)
update below.*UPDATE*
If you downloaded SQL Server 2005 SP2 before March 5, 2007 please read
article 933508 in the Microsoft Knowledge Base regarding an important issue
with SP2 and related tools that are now available for download. If you have
any questions regarding this update, please contact Ed Lehman.
Purvin Patel
SQL Connect Admin
SQL Community Team
"Ed Lehman [MSFT]" <edle@.online.microsoft.com> wrote in message
news:eaLYcVFYHHA.2552@.TK2MSFTNGP06.phx.gbl...
> An issue was recently discovered with SQL Server 2005 SP2 which might
> impact
> customers using cleanup tasks in Maintenance Plans and SQL Server
> Integration Services packages. The issue is described in detail at
> http://support.microsoft.com/kb/933508. We have created a General
> Distribution Release (GDR) #50000939 to address this issue which is
> available for download and we have included the GDR in a refresh of the
> SP2
> installation package.
> Customers who download SP2 starting Monday, March 5th, 2007 will not need
> to
> need any further action since the refreshed SP2 installation package
> includes the necessary GDR.
> We recommend that everyone who has downloaded and installed SP2 prior to
> March 5th, 2007 apply the GDR either from Microsoft Update or by
> downloading
> it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As
> described
> in the KB article (http://support.microsoft.com/kb/933508), this is
> primarily for customers who use cleanup tasks in maintenance plans and SQL
> Server Integration Services packages.
> Maintenance Plan Changes in SQL Server 2005 SP2
> Users of SQL Server 2005 maintenance plans and SQL Server Integration
> Services should be aware of a change in SP2 that affects existing cleanup
> tasks until updated using SQL Server SP2 tools.
> Who is affected?
> You are affected if you use cleanup tasks in Maintenance Plans and SQL
> Server Integration Services packages, those plans include a History
> Cleanup
> Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2.
> Users of SQL Server 2000 legacy maintenance plans are not affected.
> What is the issue?
> When SQL Server 2005 was released, cleanup intervals were measured in
> days,
> weeks, months, or years. In response to customer feedback, SQL Server 2005
> SP2 includes significant enhancements to maintenance plans. These include
> an
> enhancement that lets users specify the cleanup interval in hours.
> The change in intervals caused the initial release of SQL Server 2005 SP2
> to
> misinterpret existing cleanup task intervals in maintenance plans and
> Integration Services packages. This can lead to the files being cleaned up
> earlier than intended. The issue is described in detail at
> http://support.microsoft.com/kb/933508.
> What if I have already installed SP2 on my server?
> If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007,
> install a general distribution release (GDR) update for those SQL Server
> 2005 SP2 installations. The GDR is available from the Microsoft Download
> Center at http://go.microsoft.com/fwlink/?LinkId=85124
> After you install this GDR, you might have to restart your computer.
> This GDR is also available through Microsoft Update, and will be applied
> automatically if you are using automatic updates. However, if you are
> using
> failover clustering, you must download and apply the GDR manually.
> Microsoft
> Update will not apply the GDR to failover cluster nodes.
> What if I haven't yet installed SP2 on my server?
> SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and
> the
> current SQL Server 2005 SP2 download is updated to resolve this issue. If
> you have not installed the initial release of SP2, you can download the
> current release and install it.
> Note: If you try to apply the SP2 refresh over a previous SP2
> installation,
> no files are updated. Instead, use the general distribution release (GDR)
> update below.
>

Microsoft SQL Server 2005 Setup The cabinet file 'Sql.cab' required for this installatio

Installing SQL 2005 install in progress sertup error :
"Microsoft SQL Server 2005 Setup The cabinet file 'Sql.cab' required for this installation is
corrupt and cannot be used"I get the same error. Anyone have any idea what causes this?
Thanks.
Marcus
"Diamondas" wrote:
> Installing SQL 2005 install in progress sertup error :
> "Microsoft SQL Server 2005 Setup The cabinet file 'Sql.cab' required for this installation is
> corrupt and cannot be used"
>
>sql

Microsoft SQL Server 2005 Setup Problem

i keep getting this message whenever i double click the setup for sql server 2005. i previously installed the sql server 2005 beta 2 and have since deleted it. i've followed the readme on uninstalling some of the beta components and tried running some program i got from microsoft.com which would uninstal the pre release- the program doesn't detect any pre-release component. i however continue to get this message and need help resolving it.

TITLE: Microsoft SQL Server 2005 Setup

SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=50000&EvtType=setup%5csqlsetupactions.cpp%40PerformSCCAction2%40sqls%3a%3aPerformSCCAction%3a%3aperform%400x11190

BUTTONS:

OK

Here are several references. Check the ones you haven't previously explored.

Remove -Error message when you install SQL Server 2005: "Beta components detected"
http://support.microsoft.com/?kbid=919394

Remove -How do I remove previous versions of SQL Server 2005 / Whidbey?
http://www.aspfaq.com/sql2005/show.asp?id=15

Remove -How to uninstall an instance of SQL Server 2005 manually
http://support.microsoft.com/?kbid=909967

Remove -How to Uninstall MSDE
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991

Remove -How to Uninstall SQL Server 2005 Beta
http://go.microsoft.com/?linkid=1396133

Remove -How to uninstall SQL Server Management Studio
http://support.microsoft.com/default.aspx?scid=kb;EN-US;909953

Remove -How to use the Add or Remove Programs item in Control Panel to add
or remove components for stand-alone installations and clustered
installations of SQL Server 2005 (KB: 922670)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;922670

Remove -How to: Uninstall SQL Server Express
http://msdn2.microsoft.com/en-us/library/ms143505.aspx

Remove -The error is: Fatal error during installation"
http://support.microsoft.com/?kbid=919945

Remove -Uninstall Applications NOT in Install/Remove Programs List
http://blogs.msdn.com/astebner/archive/2005/10/30/487096.aspx

|||

Try the Windows Installer clean up tool first.

http://download.microsoft.com/download/E/9/D/E9D80355-7AB4-45B8-80E8-983A48D5E1BD/msicuu2.exe

THE INSTALLER WORKED FOR ME - -THANKS

Microsoft SQL Server 2005 Setup

i keep getting this message whenever i double click the setup for sql server 2005. i previously installed the sql server 2005 beta 2 and have since deleted it. i've followed the readme on uninstalling some of the beta components and tried running some program i got from microsoft.com which would uninstal the pre release- the program doesn't detect any pre-release component. i however continue to get this message and need help resolving it.

TITLE: Microsoft SQL Server 2005 Setup

SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=50000&EvtType=setup%5csqlsetupactions.cpp%40PerformSCCAction2%40sqls%3a%3aPerformSCCAction%3a%3aperform%400x11190

BUTTONS:

OK

Here are several references. Check the ones you haven't previously explored.

Remove -Error message when you install SQL Server 2005: "Beta components detected"
http://support.microsoft.com/?kbid=919394

Remove -How do I remove previous versions of SQL Server 2005 / Whidbey?
http://www.aspfaq.com/sql2005/show.asp?id=15

Remove -How to uninstall an instance of SQL Server 2005 manually
http://support.microsoft.com/?kbid=909967

Remove -How to Uninstall MSDE
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991

Remove -How to Uninstall SQL Server 2005 Beta
http://go.microsoft.com/?linkid=1396133

Remove -How to uninstall SQL Server Management Studio
http://support.microsoft.com/default.aspx?scid=kb;EN-US;909953

Remove -How to use the Add or Remove Programs item in Control Panel to add
or remove components for stand-alone installations and clustered
installations of SQL Server 2005 (KB: 922670)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;922670

Remove -How to: Uninstall SQL Server Express
http://msdn2.microsoft.com/en-us/library/ms143505.aspx

Remove -The error is: Fatal error during installation"
http://support.microsoft.com/?kbid=919945

Remove -Uninstall Applications NOT in Install/Remove Programs List
http://blogs.msdn.com/astebner/archive/2005/10/30/487096.aspx

|||

Try the Windows Installer clean up tool first.

http://download.microsoft.com/download/E/9/D/E9D80355-7AB4-45B8-80E8-983A48D5E1BD/msicuu2.exe

THE INSTALLER WORKED FOR ME - -THANKS

Microsoft SQL Server 2005 RTM merge replication issues

We are trying to implement merge replication between 2 servers. Database size is around 11GB.

When I tried to create publication, snaphot agent is failing with following errror.

Error: 14151, Severity: 18, State: 1.
Replication-Replication Snapshot Subsystem: agent NBTENTSQL1X-PayDirectWeb-PayDirectPub-2 failed. The
replication agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentSqlException
Exception Message: String or binary data would be truncated.
Cannot find the object 'MSmerge_sel_4D388

The table where the snapshot is breaking contains around 169 columns. Can someone please help me get through this error ?

Are you using vertical partitioning to replicate subset of the columns of the table? You may be hitting an known issue in Microsoft SQL Server 2005 where the list of column names for the table is longer than 4K and hence gets truncated in an internal proc.

|||

Thanks Sudarshan, your reply is very helpful. No we are not using vertical partitioning.

If this is a known issue, did Microsoft have any immediate fix for it or we have wait for SQL2K5 SP2 ?

|||Please wait for SQL2K5 SP2. You can install the latest CTPs availalbe and test out that your scenarios works. If not, please reply back and we can take a look further.|||This is a known issue in SQL2K5 SP1 which is fixed in SP2.|||Does the same limitation apply to the complexity of joined tables in the filter? I'm getting an error in the snapshot agent, saying:

String or

binary data would be truncated.

Cannot find

the object 'MSmerge_ctsv_2C675AF5938E4EA1B7D0DCFF9ECAD9EB', because it does not

exist or you do not have permission.

sp_MS_marksystemobject:

Invalid object name '[dbo].[MSmerge_upd_2C675AF5938E4EA1B7

But this only happens when I add too many joined tables to the filter section of the publication.

Dan

Microsoft SQL Server 2005 RTM merge replication issues

We are trying to implement merge replication between 2 servers. Database size is around 11GB.

When I tried to create publication, snaphot agent is failing with following errror.

Error: 14151, Severity: 18, State: 1.
Replication-Replication Snapshot Subsystem: agent NBTENTSQL1X-PayDirectWeb-PayDirectPub-2 failed. The
replication agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentSqlException
Exception Message: String or binary data would be truncated.
Cannot find the object 'MSmerge_sel_4D388

The table where the snapshot is breaking contains around 169 columns. Can someone please help me get through this error ?

Are you using vertical partitioning to replicate subset of the columns of the table? You may be hitting an known issue in Microsoft SQL Server 2005 where the list of column names for the table is longer than 4K and hence gets truncated in an internal proc.

|||

Thanks Sudarshan, your reply is very helpful. No we are not using vertical partitioning.

If this is a known issue, did Microsoft have any immediate fix for it or we have wait for SQL2K5 SP2 ?

|||Please wait for SQL2K5 SP2. You can install the latest CTPs availalbe and test out that your scenarios works. If not, please reply back and we can take a look further.|||This is a known issue in SQL2K5 SP1 which is fixed in SP2.|||Does the same limitation apply to the complexity of joined tables in the filter? I'm getting an error in the snapshot agent, saying:

String or

binary data would be truncated.

Cannot find

the object 'MSmerge_ctsv_2C675AF5938E4EA1B7D0DCFF9ECAD9EB', because it does not

exist or you do not have permission.

sp_MS_marksystemobject:

Invalid object name '[dbo].[MSmerge_upd_2C675AF5938E4EA1B7

But this only happens when I add too many joined tables to the filter section of the publication.

Dan

Microsoft SQL Server 2005 Reporting Services -- Error 1303

I am trying to install Microsoft SQL Server 2005 Reporting Services, Receiving the following error

Microsoft SQL Server 2005 Reporting Services -- Error 1303. The installer has insufficient privileges to access this directory: C:\Config.Msi. The installation cannot continue. Log on as administrator or contact your system administrator.

I am already logged in as Administrator and should have all the necessary permissions to install software

Please help me.

I think you accidentally got the wrong forum for this. This is the replication forum. I suggest reposting your question in the SQL Server Reporting Services forum.

Phil Garding

|||Thankssql

Microsoft SQL Server 2005 performance

Hi,

I have a Microsoft SQL Server 2005 Enterprise installed on Windows Server 2003, and developing web application for 500 clients. So I am interested will I have any performance issues if I put in 'Articles' table, data for all 500 clients and then filter it on client ID, or should I make 500 'Articles' tables for every client one with different name and then change sqldatasource for gridview depending on which client is working on it. I will have, beside 'Articles' table, another 10 tables, which means 5500 tables total, if I use second approach, on first I will have only 11 tables. So I am asking is it better to have more tables with less data, or less tables with more data. And what are pros and cons for both approach.

Thanks a lot!

One table with different ArticleIDs is the way it should be. With proper indexes you should just be fine.

Microsoft SQL Server 2005 JDBC Driver 1.1 on Solaris

hi,

Does MS2005 JDBC Driver 1.1 support integrated security on Solaris and if so
how?

Thanks,
MarcMOn Apr 24, 10:44 am, "Marc Melancon" <mmela...@.bmc.comwrote:

Quote:

Originally Posted by

hi,
>
Does MS2005 JDBC Driver 1.1 support integrated security on Solaris and if so
how?
>
Thanks,
MarcM

There's no such thing as integrated security between Solaris and MS.