CAL question

I have a CAL to access a SQL Server that is installed on a local network. I
also have MSDE installed on my local machine.
Can I use this CAL to install the client tools of SQL Server (viz Enterprise
Manager, Query Analyzer) on my local machine to access my MSDE '
Thanx in advance,
Amol.A CAL lets you install the SQL Client tools on your PC BUT as far as
managing MSDE I'm afraid you need to be a lawyer to work that out. There are
some circumstances that allow you to use the client tools against it legally
but you would really need to speak to MS to understand what they are and
they probably won't really know either - it's a bit of a nightmare :-(
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
"Amol Kasbekar" <apk@.nospam.cbord.com> wrote in message
news:%23cymQ9ptEHA.260@.TK2MSFTNGP11.phx.gbl...
>I have a CAL to access a SQL Server that is installed on a local network. I
>also have MSDE installed on my local machine.
> Can I use this CAL to install the client tools of SQL Server (viz
> Enterprise Manager, Query Analyzer) on my local machine to access my MSDE
> '
> Thanx in advance,
> Amol.
>|||Wasn't the license for the Client Tools granted only with Visual Studio,
Office Developer and SQL Server?
AFAIK, having a CAL to access SQL Server doesn't give you the rights to use
their client tools to do so, and less if you plan to admin a *gasp* free
product.
Now regarding MSDE, there are some free alternatives to EM like DbaMgr and
Visendo SQL Admin. Go google them!
Regards,
Eric Garza
AMIGE
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:eN2BLcstEHA.2788@.TK2MSFTNGP09.phx.gbl...
> A CAL lets you install the SQL Client tools on your PC BUT as far as
> managing MSDE I'm afraid you need to be a lawyer to work that out. There
are
> some circumstances that allow you to use the client tools against it
legally
> but you would really need to speak to MS to understand what they are and
> they probably won't really know either - it's a bit of a nightmare :-(
> --
> 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
> "Amol Kasbekar" <apk@.nospam.cbord.com> wrote in message
> news:%23cymQ9ptEHA.260@.TK2MSFTNGP11.phx.gbl...
I[vbcol=seagreen]
MSDE[vbcol=seagreen]
>

CAL question

I have a CAL to access a SQL Server that is installed on a local network. I
also have MSDE installed on my local machine.
Can I use this CAL to install the client tools of SQL Server (viz Enterprise
Manager, Query Analyzer) on my local machine to access my MSDE '
Thanx in advance,
Amol.A CAL lets you install the SQL Client tools on your PC BUT as far as
managing MSDE I'm afraid you need to be a lawyer to work that out. There are
some circumstances that allow you to use the client tools against it legally
but you would really need to speak to MS to understand what they are and
they probably won't really know either - it's a bit of a nightmare :-(
--
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
"Amol Kasbekar" <apk@.nospam.cbord.com> wrote in message
news:%23cymQ9ptEHA.260@.TK2MSFTNGP11.phx.gbl...
>I have a CAL to access a SQL Server that is installed on a local network. I
>also have MSDE installed on my local machine.
> Can I use this CAL to install the client tools of SQL Server (viz
> Enterprise Manager, Query Analyzer) on my local machine to access my MSDE
> '
> Thanx in advance,
> Amol.
>|||Wasn't the license for the Client Tools granted only with Visual Studio,
Office Developer and SQL Server?
AFAIK, having a CAL to access SQL Server doesn't give you the rights to use
their client tools to do so, and less if you plan to admin a *gasp* free
product.
Now regarding MSDE, there are some free alternatives to EM like DbaMgr and
Visendo SQL Admin. Go google them!
--
Regards,
Eric Garza
AMIGE
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:eN2BLcstEHA.2788@.TK2MSFTNGP09.phx.gbl...
> A CAL lets you install the SQL Client tools on your PC BUT as far as
> managing MSDE I'm afraid you need to be a lawyer to work that out. There
are
> some circumstances that allow you to use the client tools against it
legally
> but you would really need to speak to MS to understand what they are and
> they probably won't really know either - it's a bit of a nightmare :-(
> --
> 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
> "Amol Kasbekar" <apk@.nospam.cbord.com> wrote in message
> news:%23cymQ9ptEHA.260@.TK2MSFTNGP11.phx.gbl...
> >I have a CAL to access a SQL Server that is installed on a local network.
I
> >also have MSDE installed on my local machine.
> > Can I use this CAL to install the client tools of SQL Server (viz
> > Enterprise Manager, Query Analyzer) on my local machine to access my
MSDE
> > '
> >
> > Thanx in advance,
> > Amol.
> >
>

CAL question

I have a CAL to access a SQL Server that is installed on a local network. I
also have MSDE installed on my local machine.
Can I use this CAL to install the client tools of SQL Server (viz Enterprise
Manager, Query Analyzer) on my local machine to access my MSDE ?
Thanx in advance,
Amol.
A CAL lets you install the SQL Client tools on your PC BUT as far as
managing MSDE I'm afraid you need to be a lawyer to work that out. There are
some circumstances that allow you to use the client tools against it legally
but you would really need to speak to MS to understand what they are and
they probably won't really know either - it's a bit of a nightmare :-(
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
"Amol Kasbekar" <apk@.nospam.cbord.com> wrote in message
news:%23cymQ9ptEHA.260@.TK2MSFTNGP11.phx.gbl...
>I have a CAL to access a SQL Server that is installed on a local network. I
>also have MSDE installed on my local machine.
> Can I use this CAL to install the client tools of SQL Server (viz
> Enterprise Manager, Query Analyzer) on my local machine to access my MSDE
> ?
> Thanx in advance,
> Amol.
>
|||Wasn't the license for the Client Tools granted only with Visual Studio,
Office Developer and SQL Server?
AFAIK, having a CAL to access SQL Server doesn't give you the rights to use
their client tools to do so, and less if you plan to admin a *gasp* free
product.
Now regarding MSDE, there are some free alternatives to EM like DbaMgr and
Visendo SQL Admin. Go google them!
Regards,
Eric Garza
AMIGE
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:eN2BLcstEHA.2788@.TK2MSFTNGP09.phx.gbl...
> A CAL lets you install the SQL Client tools on your PC BUT as far as
> managing MSDE I'm afraid you need to be a lawyer to work that out. There
are
> some circumstances that allow you to use the client tools against it
legally[vbcol=seagreen]
> but you would really need to speak to MS to understand what they are and
> they probably won't really know either - it's a bit of a nightmare :-(
> --
> 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
> "Amol Kasbekar" <apk@.nospam.cbord.com> wrote in message
> news:%23cymQ9ptEHA.260@.TK2MSFTNGP11.phx.gbl...
I[vbcol=seagreen]
MSDE
>

CAL for MSDE for web site ?

I'm building a web site using MSDE (Rel A) & Visual Studio. Do I have to have any sort of licence to use MSDE ? If so, is it covered by the Visual Studio and/or redistribution rights under Release A ?
Sarah,
You can find vast info here on msde.
http://www.microsoft.com/sql/msde/
-oj
http://www.rac4sql.net
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:53059AD9-694E-4BF0-A57B-86C379D9A0C6@.microsoft.com...
> I'm building a web site using MSDE (Rel A) & Visual Studio. Do I have to have
any sort of licence to use MSDE ? If so, is it covered by the Visual Studio
and/or redistribution rights under Release A ?

c# 2005 express edition install difficulty

I just installed express and found out that it won't connect to any of our
production Sql Server 2000 data or Sql Server 2003 MSDE (my local
development db). Another one of our developers installed Sql Server 2005
express with the c# 2005 express and couldn't connect to his production box
(also SS 2000) and screwed up Enterprise manager.
Has anyone else had this problem'Peter
> express with the c# 2005 express and couldn't connect to his production
> box (also SS 2000) and screwed up Enterprise manager.
>
Any errors?
"Peter Lux" <pete.lux@.theheritagegrp.com> wrote in message
news:ubejqfDSGHA.4608@.tk2msftngp13.phx.gbl...
>I just installed express and found out that it won't connect to any of our
>production Sql Server 2000 data or Sql Server 2003 MSDE (my local
>development db). Another one of our developers installed Sql Server 2005
>express with the c# 2005 express and couldn't connect to his production box
>(also SS 2000) and screwed up Enterprise manager.
> Has anyone else had this problem'
>|||The default setup of Express Edition does not enable network connection from
off the box where it is installed. Have you enabled network connections and
opened any firewalls to allow connections?
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
"Peter Lux" <pete.lux@.theheritagegrp.com> wrote in message
news:ubejqfDSGHA.4608@.tk2msftngp13.phx.gbl...
>I just installed express and found out that it won't connect to any of our
>production Sql Server 2000 data or Sql Server 2003 MSDE (my local
>development db). Another one of our developers installed Sql Server 2005
>express with the c# 2005 express and couldn't connect to his production box
>(also SS 2000) and screwed up Enterprise manager.
> Has anyone else had this problem'
>

C# - Need to find instances of SQL Server on client

How can I determine using C# which instances of SQL Server 2000,
MSDE, 2005 or 2005 Express, if any, are installed on a client
computer?
For instance, by knowing the computer's name, I could
guess at a named instance of the data provider and use
it in a connection string, assuming Windows Integrated
Security, and attempt a connection. But this is klutzy.
Is there a method of *discovery* that returns the info?
In Visual Studio 2003/2005 when attempting a new connection
in Server Explorer, an applet appears which does something
like this. Ditto in SQL Server Manager.
The intent is to use DDL, embedded in ADO.Net library
calls, to create a data schema for an application
with stored procedures. This part is easy. But first,
I need to know "who's" there.
Hi,
This enum in C# can help you.
http://blogs.msdn.com/sushilc/archive/2004/10/14/242395.aspx
Thanks
Omar
"Stratum" wrote:

> How can I determine using C# which instances of SQL Server 2000,
> MSDE, 2005 or 2005 Express, if any, are installed on a client
> computer?
> For instance, by knowing the computer's name, I could
> guess at a named instance of the data provider and use
> it in a connection string, assuming Windows Integrated
> Security, and attempt a connection. But this is klutzy.
> Is there a method of *discovery* that returns the info?
> In Visual Studio 2003/2005 when attempting a new connection
> in Server Explorer, an applet appears which does something
> like this. Ditto in SQL Server Manager.
> The intent is to use DDL, embedded in ADO.Net library
> calls, to create a data schema for an application
> with stored procedures. This part is easy. But first,
> I need to know "who's" there.
>

Buy SQL Server 2000 or...

Hi all,
I just need an opinion -
The organization I work for is considering buying the "full version" of SQL
Server 2000 (we're using MSDE 2000 right now).
The thing is, since we're in 2004, I'm worried that the next big version of
SQL Server could be somewhere around the corner.
(The present version's capabilities are absolutely convenient for our needs
now and as far as I can see in the future.)
Our server is running on Windows 2000, and maybe we'll move to Windows 2003
some time next year.
So here are my questions:
- Is it worth it to invest substantial money in SQL Server 2000 now or
should we cope with MSDE and wait for the next release;
- If we're going with the 2000 version, and since the life cycle of server
products tends to be a bit longer than destop products, how many years from
now is it reasonable to think that it would be supported ?
TIA
Paul Dussault, MCPThe next version is SQL Server 2005 ("Yukon") which Microsoft has announced
for the first half of 2005.
Microsoft's support lifecycle policies are documented here:
http://support.microsoft.com/default.aspx?pr=lifecycle
This states that Mainstream Support for SQLServer 2000 will end 31 December
2005. In view of the projected release date of Yukon I wouldn't be surprised
if the end date of the Mainstream Support period was pushed back. Extended
Support ends 31 December 2007.
I would suggest that if SQL2000 meets your requirements and is going to
bring benefits to your organization today then there is no reason to wait.
David Portas
SQL Server MVP
--|||It is expected that Yukon (the next version of SQL Server) will be =
released some time next year. If you need to upgrade to SQL Server it =
might be good to do so now. SQL Server 2000 will probably be supported =
until the version of SQL Server after Yukon is released, so SQL Server =
2000 will probabaly be supported for a while. =20
If you have a database with many users I am guessing that SQL Server =
will probably perform better than MSDE. With that said, I cannot tell =
you what to do. How is MSDE performing for you? You mentioned =
"substancial money" ...do you have to buy a new server, or are you =
talking about license cost? =20
--=20
Keith
"Paul Dussault" <paulduss@.hotmail.com> wrote in message =
news:%23ArQuNDNEHA.2780@.TK2MSFTNGP09.phx.gbl...
> Hi all,
>=20
> I just need an opinion -
>=20
> The organization I work for is considering buying the "full version" =
of SQL
> Server 2000 (we're using MSDE 2000 right now).
> The thing is, since we're in 2004, I'm worried that the next big =
version of
> SQL Server could be somewhere around the corner.
> (The present version's capabilities are absolutely convenient for our =
needs
> now and as far as I can see in the future.)
> Our server is running on Windows 2000, and maybe we'll move to Windows =
2003
> some time next year.
>=20
> So here are my questions:
>=20
> - Is it worth it to invest substantial money in SQL Server 2000 now or
> should we cope with MSDE and wait for the next release;
> - If we're going with the 2000 version, and since the life cycle of =
server
> products tends to be a bit longer than destop products, how many years =
from
> now is it reasonable to think that it would be supported ?
>=20
>=20
> TIA
>=20
>=20
> Paul Dussault, MCP
>=20
>|||I'm assuming it's likely that you have a business reason for asking - i.e. M
SDE is struggling to meet your demands? If that's so - then it depends how m
uch your business wants to move forward. If you've properly evaluated SQL2k
then it may be an idea to i
ntroduce a product which has been serviced packed several times and is very
stable rather than waiting for a new product and the development/bedding in
process' you may need.
Julie
http://www.sqlporn.co.uk :o)|||Hi Keith,

> If you have a database with many users I am guessing that SQL Server will
probably perform better than MSDE.
For now we have just a few apps with just a few users. But many more apps
and Web sites are in planning or in development, so we're bound to work with
the full version at one time or another.

> How is MSDE performing for you? You mentioned "substancial money" ...do
you have to buy a new server, or are you talking about license cost?
MSDE is OK right now. And we have a brand new server and it rocks. I
personally think that SQL Server 2000 will be supported for a while; but I
have to sit with management and will have to deal with their perception:
"why should we buy a 3000$ product that is 4 year old, to replace a product
that's working fine and is... free?"
You get the idea... So I'll need all the arguments I can get (and a few
experts opinions could do no harm!) to convince them that it's a worthy
purchase...
Thanks for your input!
Paul Dussault, MCP
Keith
"Paul Dussault" <paulduss@.hotmail.com> wrote in message
news:%23ArQuNDNEHA.2780@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> I just need an opinion -
> The organization I work for is considering buying the "full version" of
SQL
> Server 2000 (we're using MSDE 2000 right now).
> The thing is, since we're in 2004, I'm worried that the next big version
of
> SQL Server could be somewhere around the corner.
> (The present version's capabilities are absolutely convenient for our
needs
> now and as far as I can see in the future.)
> Our server is running on Windows 2000, and maybe we'll move to Windows
2003
> some time next year.
> So here are my questions:
> - Is it worth it to invest substantial money in SQL Server 2000 now or
> should we cope with MSDE and wait for the next release;
> - If we're going with the 2000 version, and since the life cycle of server
> products tends to be a bit longer than destop products, how many years
from
> now is it reasonable to think that it would be supported ?
>
> TIA
>
> Paul Dussault, MCP
>|||Thanks David,
This kind of data will be helpful.
Paul Dussault, MCP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:luidnetW86CJCwbdRVn-gw@.giganews.com...
> The next version is SQL Server 2005 ("Yukon") which Microsoft has
announced
> for the first half of 2005.
> Microsoft's support lifecycle policies are documented here:
> http://support.microsoft.com/default.aspx?pr=lifecycle
> This states that Mainstream Support for SQLServer 2000 will end 31
December
> 2005. In view of the projected release date of Yukon I wouldn't be
surprised
> if the end date of the Mainstream Support period was pushed back. Extended
> Support ends 31 December 2007.
> I would suggest that if SQL2000 meets your requirements and is going to
> bring benefits to your organization today then there is no reason to wait.
> --
> David Portas
> SQL Server MVP
> --
>|||..this maybe somewhere to start?
http://www.teratrax.com/articles/ms...sql_server.html|||Thanks Julie,
This will be a good read for my bosses indeed.
Paul Dussault, MCP
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:B71D98AC-4EEB-4C1E-AF95-4C17A592B25A@.microsoft.com...
> ..this maybe somewhere to start?
> http://www.teratrax.com/articles/ms...sql_server.html|||Paul,
A tip if you aren't already aware of it:
You can use DBCC CONCURRENCYVIOLATION to monitor how often etc. the performa
nce throttling has kicked in. This
might buy you some time, and perhaps the support plans for SQL2K has been up
dated by the time this reports any
significant throttling...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Paul Dussault" <paulduss@.hotmail.com> wrote in message news:uQ6buGENEHA.3476@.TK2MSFTNGP09.p
hx.gbl...
> Hi Keith,
>
> probably perform better than MSDE.
> For now we have just a few apps with just a few users. But many more apps
> and Web sites are in planning or in development, so we're bound to work wi
th
> the full version at one time or another.
>
> you have to buy a new server, or are you talking about license cost?
> MSDE is OK right now. And we have a brand new server and it rocks. I
> personally think that SQL Server 2000 will be supported for a while; but I
> have to sit with management and will have to deal with their perception:
> "why should we buy a 3000$ product that is 4 year old, to replace a produc
t
> that's working fine and is... free?"
> You get the idea... So I'll need all the arguments I can get (and a few
> experts opinions could do no harm!) to convince them that it's a worthy
> purchase...
> Thanks for your input!
>
> Paul Dussault, MCP
> --
> Keith
>
> "Paul Dussault" <paulduss@.hotmail.com> wrote in message
> news:%23ArQuNDNEHA.2780@.TK2MSFTNGP09.phx.gbl...
> SQL
> of
> needs
> 2003
> from
>

Buy SQL Server 2000 or...

Hi all,
I just need an opinion -
The organization I work for is considering buying the "full version" of SQL
Server 2000 (we're using MSDE 2000 right now).
The thing is, since we're in 2004, I'm worried that the next big version of
SQL Server could be somewhere around the corner.
(The present version's capabilities are absolutely convenient for our needs
now and as far as I can see in the future.)
Our server is running on Windows 2000, and maybe we'll move to Windows 2003
some time next year.
So here are my questions:
- Is it worth it to invest substantial money in SQL Server 2000 now or
should we cope with MSDE and wait for the next release;
- If we're going with the 2000 version, and since the life cycle of server
products tends to be a bit longer than destop products, how many years from
now is it reasonable to think that it would be supported ?
TIA
Paul Dussault, MCPThe next version is SQL Server 2005 ("Yukon") which Microsoft has announced
for the first half of 2005.
Microsoft's support lifecycle policies are documented here:
http://support.microsoft.com/default.aspx?pr=lifecycle
This states that Mainstream Support for SQLServer 2000 will end 31 December
2005. In view of the projected release date of Yukon I wouldn't be surprised
if the end date of the Mainstream Support period was pushed back. Extended
Support ends 31 December 2007.
I would suggest that if SQL2000 meets your requirements and is going to
bring benefits to your organization today then there is no reason to wait.
--
David Portas
SQL Server MVP
--|||It is expected that Yukon (the next version of SQL Server) will be =released some time next year. If you need to upgrade to SQL Server it =might be good to do so now. SQL Server 2000 will probably be supported =until the version of SQL Server after Yukon is released, so SQL Server =2000 will probabaly be supported for a while.
If you have a database with many users I am guessing that SQL Server =will probably perform better than MSDE. With that said, I cannot tell =you what to do. How is MSDE performing for you? You mentioned ="substancial money" ...do you have to buy a new server, or are you =talking about license cost? -- Keith
"Paul Dussault" <paulduss@.hotmail.com> wrote in message =news:%23ArQuNDNEHA.2780@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> > I just need an opinion -
> > The organization I work for is considering buying the "full version" =of SQL
> Server 2000 (we're using MSDE 2000 right now).
> The thing is, since we're in 2004, I'm worried that the next big =version of
> SQL Server could be somewhere around the corner.
> (The present version's capabilities are absolutely convenient for our =needs
> now and as far as I can see in the future.)
> Our server is running on Windows 2000, and maybe we'll move to Windows =2003
> some time next year.
> > So here are my questions:
> > - Is it worth it to invest substantial money in SQL Server 2000 now or
> should we cope with MSDE and wait for the next release;
> - If we're going with the 2000 version, and since the life cycle of =server
> products tends to be a bit longer than destop products, how many years =from
> now is it reasonable to think that it would be supported ?
> > > TIA
> > > Paul Dussault, MCP
> >|||Hi Keith,
> If you have a database with many users I am guessing that SQL Server will
probably perform better than MSDE.
For now we have just a few apps with just a few users. But many more apps
and Web sites are in planning or in development, so we're bound to work with
the full version at one time or another.
> How is MSDE performing for you? You mentioned "substancial money" ...do
you have to buy a new server, or are you talking about license cost?
MSDE is OK right now. And we have a brand new server and it rocks. I
personally think that SQL Server 2000 will be supported for a while; but I
have to sit with management and will have to deal with their perception:
"why should we buy a 3000$ product that is 4 year old, to replace a product
that's working fine and is... free?"
You get the idea... So I'll need all the arguments I can get (and a few
experts opinions could do no harm!) to convince them that it's a worthy
purchase...
Thanks for your input!
Paul Dussault, MCP
--
Keith
"Paul Dussault" <paulduss@.hotmail.com> wrote in message
news:%23ArQuNDNEHA.2780@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> I just need an opinion -
> The organization I work for is considering buying the "full version" of
SQL
> Server 2000 (we're using MSDE 2000 right now).
> The thing is, since we're in 2004, I'm worried that the next big version
of
> SQL Server could be somewhere around the corner.
> (The present version's capabilities are absolutely convenient for our
needs
> now and as far as I can see in the future.)
> Our server is running on Windows 2000, and maybe we'll move to Windows
2003
> some time next year.
> So here are my questions:
> - Is it worth it to invest substantial money in SQL Server 2000 now or
> should we cope with MSDE and wait for the next release;
> - If we're going with the 2000 version, and since the life cycle of server
> products tends to be a bit longer than destop products, how many years
from
> now is it reasonable to think that it would be supported ?
>
> TIA
>
> Paul Dussault, MCP
>|||Thanks David,
This kind of data will be helpful.
Paul Dussault, MCP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:luidnetW86CJCwbdRVn-gw@.giganews.com...
> The next version is SQL Server 2005 ("Yukon") which Microsoft has
announced
> for the first half of 2005.
> Microsoft's support lifecycle policies are documented here:
> http://support.microsoft.com/default.aspx?pr=lifecycle
> This states that Mainstream Support for SQLServer 2000 will end 31
December
> 2005. In view of the projected release date of Yukon I wouldn't be
surprised
> if the end date of the Mainstream Support period was pushed back. Extended
> Support ends 31 December 2007.
> I would suggest that if SQL2000 meets your requirements and is going to
> bring benefits to your organization today then there is no reason to wait.
> --
> David Portas
> SQL Server MVP
> --
>|||Thanks Julie,
This will be a good read for my bosses indeed.
Paul Dussault, MCP
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:B71D98AC-4EEB-4C1E-AF95-4C17A592B25A@.microsoft.com...
> ..this maybe somewhere to start?
> http://www.teratrax.com/articles/msde_vs_sql_server.html|||Paul,
A tip if you aren't already aware of it:
You can use DBCC CONCURRENCYVIOLATION to monitor how often etc. the performance throttling has kicked in. This
might buy you some time, and perhaps the support plans for SQL2K has been updated by the time this reports any
significant throttling...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Paul Dussault" <paulduss@.hotmail.com> wrote in message news:uQ6buGENEHA.3476@.TK2MSFTNGP09.phx.gbl...
> Hi Keith,
> > If you have a database with many users I am guessing that SQL Server will
> probably perform better than MSDE.
> For now we have just a few apps with just a few users. But many more apps
> and Web sites are in planning or in development, so we're bound to work with
> the full version at one time or another.
> > How is MSDE performing for you? You mentioned "substancial money" ...do
> you have to buy a new server, or are you talking about license cost?
> MSDE is OK right now. And we have a brand new server and it rocks. I
> personally think that SQL Server 2000 will be supported for a while; but I
> have to sit with management and will have to deal with their perception:
> "why should we buy a 3000$ product that is 4 year old, to replace a product
> that's working fine and is... free?"
> You get the idea... So I'll need all the arguments I can get (and a few
> experts opinions could do no harm!) to convince them that it's a worthy
> purchase...
> Thanks for your input!
>
> Paul Dussault, MCP
> --
> Keith
>
> "Paul Dussault" <paulduss@.hotmail.com> wrote in message
> news:%23ArQuNDNEHA.2780@.TK2MSFTNGP09.phx.gbl...
> > Hi all,
> >
> > I just need an opinion -
> >
> > The organization I work for is considering buying the "full version" of
> SQL
> > Server 2000 (we're using MSDE 2000 right now).
> > The thing is, since we're in 2004, I'm worried that the next big version
> of
> > SQL Server could be somewhere around the corner.
> > (The present version's capabilities are absolutely convenient for our
> needs
> > now and as far as I can see in the future.)
> > Our server is running on Windows 2000, and maybe we'll move to Windows
> 2003
> > some time next year.
> >
> > So here are my questions:
> >
> > - Is it worth it to invest substantial money in SQL Server 2000 now or
> > should we cope with MSDE and wait for the next release;
> > - If we're going with the 2000 version, and since the life cycle of server
> > products tends to be a bit longer than destop products, how many years
> from
> > now is it reasonable to think that it would be supported ?
> >
> >
> > TIA
> >
> >
> > Paul Dussault, MCP
> >
> >
>

Buy SQL Server 2000 or...

Hi all,
I just need an opinion -
The organization I work for is considering buying the "full version" of SQL
Server 2000 (we're using MSDE 2000 right now).
The thing is, since we're in 2004, I'm worried that the next big version of
SQL Server could be somewhere around the corner.
(The present version's capabilities are absolutely convenient for our needs
now and as far as I can see in the future.)
Our server is running on Windows 2000, and maybe we'll move to Windows 2003
some time next year.
So here are my questions:
- Is it worth it to invest substantial money in SQL Server 2000 now or
should we cope with MSDE and wait for the next release;
- If we're going with the 2000 version, and since the life cycle of server
products tends to be a bit longer than destop products, how many years from
now is it reasonable to think that it would be supported ?
TIA
Paul Dussault, MCP
The next version is SQL Server 2005 ("Yukon") which Microsoft has announced
for the first half of 2005.
Microsoft's support lifecycle policies are documented here:
http://support.microsoft.com/default.aspx?pr=lifecycle
This states that Mainstream Support for SQLServer 2000 will end 31 December
2005. In view of the projected release date of Yukon I wouldn't be surprised
if the end date of the Mainstream Support period was pushed back. Extended
Support ends 31 December 2007.
I would suggest that if SQL2000 meets your requirements and is going to
bring benefits to your organization today then there is no reason to wait.
David Portas
SQL Server MVP
|||It is expected that Yukon (the next version of SQL Server) will be =
released some time next year. If you need to upgrade to SQL Server it =
might be good to do so now. SQL Server 2000 will probably be supported =
until the version of SQL Server after Yukon is released, so SQL Server =
2000 will probabaly be supported for a while. =20
If you have a database with many users I am guessing that SQL Server =
will probably perform better than MSDE. With that said, I cannot tell =
you what to do. How is MSDE performing for you? You mentioned =
"substancial money" ...do you have to buy a new server, or are you =
talking about license cost? =20
--=20
Keith
"Paul Dussault" <paulduss@.hotmail.com> wrote in message =
news:%23ArQuNDNEHA.2780@.TK2MSFTNGP09.phx.gbl...
> Hi all,
>=20
> I just need an opinion -
>=20
> The organization I work for is considering buying the "full version" =
of SQL
> Server 2000 (we're using MSDE 2000 right now).
> The thing is, since we're in 2004, I'm worried that the next big =
version of
> SQL Server could be somewhere around the corner.
> (The present version's capabilities are absolutely convenient for our =
needs
> now and as far as I can see in the future.)
> Our server is running on Windows 2000, and maybe we'll move to Windows =
2003
> some time next year.
>=20
> So here are my questions:
>=20
> - Is it worth it to invest substantial money in SQL Server 2000 now or
> should we cope with MSDE and wait for the next release;
> - If we're going with the 2000 version, and since the life cycle of =
server
> products tends to be a bit longer than destop products, how many years =
from
> now is it reasonable to think that it would be supported ?
>=20
>=20
> TIA
>=20
>=20
> Paul Dussault, MCP
>=20
>
|||I'm assuming it's likely that you have a business reason for asking - i.e. MSDE is struggling to meet your demands? If that's so - then it depends how much your business wants to move forward. If you've properly evaluated SQL2k then it may be an idea to i
ntroduce a product which has been serviced packed several times and is very stable rather than waiting for a new product and the development/bedding in process' you may need.
Julie
http://www.sqlporn.co.uk :o)
|||Hi Keith,

> If you have a database with many users I am guessing that SQL Server will
probably perform better than MSDE.
For now we have just a few apps with just a few users. But many more apps
and Web sites are in planning or in development, so we're bound to work with
the full version at one time or another.

> How is MSDE performing for you? You mentioned "substancial money" ...do
you have to buy a new server, or are you talking about license cost?
MSDE is OK right now. And we have a brand new server and it rocks. I
personally think that SQL Server 2000 will be supported for a while; but I
have to sit with management and will have to deal with their perception:
"why should we buy a 3000$ product that is 4 year old, to replace a product
that's working fine and is... free?"
You get the idea... So I'll need all the arguments I can get (and a few
experts opinions could do no harm!) to convince them that it's a worthy
purchase...
Thanks for your input!
Paul Dussault, MCP
Keith
"Paul Dussault" <paulduss@.hotmail.com> wrote in message
news:%23ArQuNDNEHA.2780@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> I just need an opinion -
> The organization I work for is considering buying the "full version" of
SQL
> Server 2000 (we're using MSDE 2000 right now).
> The thing is, since we're in 2004, I'm worried that the next big version
of
> SQL Server could be somewhere around the corner.
> (The present version's capabilities are absolutely convenient for our
needs
> now and as far as I can see in the future.)
> Our server is running on Windows 2000, and maybe we'll move to Windows
2003
> some time next year.
> So here are my questions:
> - Is it worth it to invest substantial money in SQL Server 2000 now or
> should we cope with MSDE and wait for the next release;
> - If we're going with the 2000 version, and since the life cycle of server
> products tends to be a bit longer than destop products, how many years
from
> now is it reasonable to think that it would be supported ?
>
> TIA
>
> Paul Dussault, MCP
>
|||Thanks David,
This kind of data will be helpful.
Paul Dussault, MCP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:luidnetW86CJCwbdRVn-gw@.giganews.com...
> The next version is SQL Server 2005 ("Yukon") which Microsoft has
announced
> for the first half of 2005.
> Microsoft's support lifecycle policies are documented here:
> http://support.microsoft.com/default.aspx?pr=lifecycle
> This states that Mainstream Support for SQLServer 2000 will end 31
December
> 2005. In view of the projected release date of Yukon I wouldn't be
surprised
> if the end date of the Mainstream Support period was pushed back. Extended
> Support ends 31 December 2007.
> I would suggest that if SQL2000 meets your requirements and is going to
> bring benefits to your organization today then there is no reason to wait.
> --
> David Portas
> SQL Server MVP
> --
>
|||...this maybe somewhere to start?
http://www.teratrax.com/articles/msd...ql_server.html
|||Thanks Julie,
This will be a good read for my bosses indeed.
Paul Dussault, MCP
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:B71D98AC-4EEB-4C1E-AF95-4C17A592B25A@.microsoft.com...
> ..this maybe somewhere to start?
> http://www.teratrax.com/articles/msd...ql_server.html
|||Paul,
A tip if you aren't already aware of it:
You can use DBCC CONCURRENCYVIOLATION to monitor how often etc. the performance throttling has kicked in. This
might buy you some time, and perhaps the support plans for SQL2K has been updated by the time this reports any
significant throttling...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Paul Dussault" <paulduss@.hotmail.com> wrote in message news:uQ6buGENEHA.3476@.TK2MSFTNGP09.phx.gbl...
> Hi Keith,
> probably perform better than MSDE.
> For now we have just a few apps with just a few users. But many more apps
> and Web sites are in planning or in development, so we're bound to work with
> the full version at one time or another.
> you have to buy a new server, or are you talking about license cost?
> MSDE is OK right now. And we have a brand new server and it rocks. I
> personally think that SQL Server 2000 will be supported for a while; but I
> have to sit with management and will have to deal with their perception:
> "why should we buy a 3000$ product that is 4 year old, to replace a product
> that's working fine and is... free?"
> You get the idea... So I'll need all the arguments I can get (and a few
> experts opinions could do no harm!) to convince them that it's a worthy
> purchase...
> Thanks for your input!
>
> Paul Dussault, MCP
> --
> Keith
>
> "Paul Dussault" <paulduss@.hotmail.com> wrote in message
> news:%23ArQuNDNEHA.2780@.TK2MSFTNGP09.phx.gbl...
> SQL
> of
> needs
> 2003
> from
>

Buy Enterprise or Standard Edition

Dear Experts,
Right now i am doing a development using MSDE 7.0 and VB. Soon this
development will be completed (Hopefully!!!) and i will have to recommend to
a prospective client a version of SQL Server. The application is quiet small
for about 6 to 8 users. I would appreciate if you could throw some light on
the version of SQL Server i may need.
If the client wants to buy the latest i.e. Sql Server 2005 then will there
be any conversion problems from 7.0
Thanks for Help and like always thanks for passing your expert knowledge
Regards
Manish Sawjiani
--
Three Cheers to Technet for the Help!Hi Manish
Just Check this. This might be useful to yo
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8ynn.asp
--
best Regards,
Chandra
http://chanduas.blogspot.com/
---
"Manish Sawjiani" wrote:
> Dear Experts,
> Right now i am doing a development using MSDE 7.0 and VB. Soon this
> development will be completed (Hopefully!!!) and i will have to recommend to
> a prospective client a version of SQL Server. The application is quiet small
> for about 6 to 8 users. I would appreciate if you could throw some light on
> the version of SQL Server i may need.
> If the client wants to buy the latest i.e. Sql Server 2005 then will there
> be any conversion problems from 7.0
> Thanks for Help and like always thanks for passing your expert knowledge
> Regards
> Manish Sawjiani
> --
> Three Cheers to Technet for the Help!|||Go to www.microsoft.com/sql and read about the editions available. Note that there recently has been
released a "workgroup" edition.
> If the client wants to buy the latest i.e. Sql Server 2005 then will there
> be any conversion problems from 7.0
Are you asking of your code will still work? Probably, but you need to plan for test and possibly
(although unlikely) code changes between 7.0 and 2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in message
news:F4CFED90-C7FC-484C-B409-C5A75F990EE8@.microsoft.com...
> Dear Experts,
> Right now i am doing a development using MSDE 7.0 and VB. Soon this
> development will be completed (Hopefully!!!) and i will have to recommend to
> a prospective client a version of SQL Server. The application is quiet small
> for about 6 to 8 users. I would appreciate if you could throw some light on
> the version of SQL Server i may need.
> If the client wants to buy the latest i.e. Sql Server 2005 then will there
> be any conversion problems from 7.0
> Thanks for Help and like always thanks for passing your expert knowledge
> Regards
> Manish Sawjiani
> --
> Three Cheers to Technet for the Help!

Buy Enterprise or Standard Edition

Dear Experts,
Right now i am doing a development using MSDE 7.0 and VB. Soon this
development will be completed (Hopefully!!!) and i will have to recommend to
a prospective client a version of SQL Server. The application is quiet small
for about 6 to 8 users. I would appreciate if you could throw some light on
the version of SQL Server i may need.
If the client wants to buy the latest i.e. Sql Server 2005 then will there
be any conversion problems from 7.0
Thanks for Help and like always thanks for passing your expert knowledge
Regards
Manish Sawjiani
--
Three Cheers to technet for the Help!Hi Manish
Just Check this. This might be useful to you
http://msdn.microsoft.com/library/d...br />
8ynn.asp
best Regards,
Chandra
http://chanduas.blogspot.com/
---
"Manish Sawjiani" wrote:

> Dear Experts,
> Right now i am doing a development using MSDE 7.0 and VB. Soon this
> development will be completed (Hopefully!!!) and i will have to recommend
to
> a prospective client a version of SQL Server. The application is quiet sma
ll
> for about 6 to 8 users. I would appreciate if you could throw some light o
n
> the version of SQL Server i may need.
> If the client wants to buy the latest i.e. Sql Server 2005 then will there
> be any conversion problems from 7.0
> Thanks for Help and like always thanks for passing your expert knowledge
> Regards
> Manish Sawjiani
> --
> Three Cheers to technet for the Help!|||Go to www.microsoft.com/sql and read about the editions available. Note that
there recently has been
released a "workgroup" edition.

> If the client wants to buy the latest i.e. Sql Server 2005 then will there
> be any conversion problems from 7.0
Are you asking of your code will still work? Probably, but you need to plan
for test and possibly
(although unlikely) code changes between 7.0 and 2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in messag
e
news:F4CFED90-C7FC-484C-B409-C5A75F990EE8@.microsoft.com...
> Dear Experts,
> Right now i am doing a development using MSDE 7.0 and VB. Soon this
> development will be completed (Hopefully!!!) and i will have to recommend
to
> a prospective client a version of SQL Server. The application is quiet sma
ll
> for about 6 to 8 users. I would appreciate if you could throw some light o
n
> the version of SQL Server i may need.
> If the client wants to buy the latest i.e. Sql Server 2005 then will there
> be any conversion problems from 7.0
> Thanks for Help and like always thanks for passing your expert knowledge
> Regards
> Manish Sawjiani
> --
> Three Cheers to technet for the Help!

Buy Enterprise or Standard Edition

Dear Experts,
Right now i am doing a development using MSDE 7.0 and VB. Soon this
development will be completed (Hopefully!!!) and i will have to recommend to
a prospective client a version of SQL Server. The application is quiet small
for about 6 to 8 users. I would appreciate if you could throw some light on
the version of SQL Server i may need.
If the client wants to buy the latest i.e. Sql Server 2005 then will there
be any conversion problems from 7.0
Thanks for Help and like always thanks for passing your expert knowledge
Regards
Manish Sawjiani
Three Cheers to Technet for the Help!
Hi Manish
Just Check this. This might be useful to you
http://msdn.microsoft.com/library/de...ar_ts_8ynn.asp
best Regards,
Chandra
http://chanduas.blogspot.com/
"Manish Sawjiani" wrote:

> Dear Experts,
> Right now i am doing a development using MSDE 7.0 and VB. Soon this
> development will be completed (Hopefully!!!) and i will have to recommend to
> a prospective client a version of SQL Server. The application is quiet small
> for about 6 to 8 users. I would appreciate if you could throw some light on
> the version of SQL Server i may need.
> If the client wants to buy the latest i.e. Sql Server 2005 then will there
> be any conversion problems from 7.0
> Thanks for Help and like always thanks for passing your expert knowledge
> Regards
> Manish Sawjiani
> --
> Three Cheers to Technet for the Help!
|||Go to www.microsoft.com/sql and read about the editions available. Note that there recently has been
released a "workgroup" edition.

> If the client wants to buy the latest i.e. Sql Server 2005 then will there
> be any conversion problems from 7.0
Are you asking of your code will still work? Probably, but you need to plan for test and possibly
(although unlikely) code changes between 7.0 and 2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> wrote in message
news:F4CFED90-C7FC-484C-B409-C5A75F990EE8@.microsoft.com...
> Dear Experts,
> Right now i am doing a development using MSDE 7.0 and VB. Soon this
> development will be completed (Hopefully!!!) and i will have to recommend to
> a prospective client a version of SQL Server. The application is quiet small
> for about 6 to 8 users. I would appreciate if you could throw some light on
> the version of SQL Server i may need.
> If the client wants to buy the latest i.e. Sql Server 2005 then will there
> be any conversion problems from 7.0
> Thanks for Help and like always thanks for passing your expert knowledge
> Regards
> Manish Sawjiani
> --
> Three Cheers to Technet for the Help!