Hi.
We have Windows 2000 Small Business Server
In control panel/System the operating system is identified
as
Windows 2000 server service pack 4
Microsoft pages on System requirements for SQL Server
Enterprise edition says requires Windows 2000 Server
The operating system I have seems to be Windows 2000
Server even though it has some junk in it making it
Windows 2000 Small Business Server.
Question can i Install SQL Server 2000 Enterprise?
I need this because i need to use Indexed Views which do
not exist in Sql Server standard edition.
THe answer varies depending on whome i ask at Microsoft.
Apreciate any advice.Hi
There is no mention of SBS on the system requirements at
http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.asp
even though SQL Server comes with it!!
I have never tried installing this onto a specific SBS system, so can not be
100% but I am pretty sure that it is no different. If you do help/about
windows in Windows Explorer and it says Microsoft (R) Windows Version 5.0
then I don't think there would be any reason for it not to.
John
"Wayne Wilson" <anonymous@.discussions.microsoft.com> wrote in message
news:904101c43310$657e3600$a101280a@.phx.gbl...
> Hi.
> We have Windows 2000 Small Business Server
> In control panel/System the operating system is identified
> as
> Windows 2000 server service pack 4
> Microsoft pages on System requirements for SQL Server
> Enterprise edition says requires Windows 2000 Server
> The operating system I have seems to be Windows 2000
> Server even though it has some junk in it making it
> Windows 2000 Small Business Server.
> Question can i Install SQL Server 2000 Enterprise?
> I need this because i need to use Indexed Views which do
> not exist in Sql Server standard edition.
> THe answer varies depending on whome i ask at Microsoft.
> Apreciate any advice.
>|||Please do not post the same message independently in different newsgroups, I
posted an answer in .setup.
--
Jacco Schalkwijk
SQL Server MVP
"Wayne Wilson" <anonymous@.discussions.microsoft.com> wrote in message
news:904101c43310$657e3600$a101280a@.phx.gbl...
> Hi.
> We have Windows 2000 Small Business Server
> In control panel/System the operating system is identified
> as
> Windows 2000 server service pack 4
> Microsoft pages on System requirements for SQL Server
> Enterprise edition says requires Windows 2000 Server
> The operating system I have seems to be Windows 2000
> Server even though it has some junk in it making it
> Windows 2000 Small Business Server.
> Question can i Install SQL Server 2000 Enterprise?
> I need this because i need to use Indexed Views which do
> not exist in Sql Server standard edition.
> THe answer varies depending on whome i ask at Microsoft.
> Apreciate any advice.
>
Showing posts with label enterprise. Show all posts
Showing posts with label enterprise. Show all posts
Thursday, March 29, 2012
Can I install a Enterprise version analysis service on a Standard version of SQL 2005 server?
Hi all,
Since some analysis services features are only available in Enterprise version , I have to upgrade my SQL 2005 server from standard edition to enterpise edition.
So I uninstall originial standard version of analysis service and install a Enterprise version. However, the analysis service is still a standard version after installation.
Is it possible to keep data engine as standard version and install a enterprise version of analysis service?
Thank you very much
Tony
Yes. This is supported as in SQL Server 2005, Standardard SKU and Enterprise SKU can be installed side by side successfully. Of course, their instancenames must be distinct.
Can I install a Enterprise version analysis service on a Standard version of SQL 2005 server
Hi all,
Since some analysis services features are only available in Enterprise version , I have to upgrade my SQL 2005 server from standard edition to enterpise edition.
So I uninstall originial standard version of analysis service and install a Enterprise version. However, the analysis service is still a standard version after installation.
Is it possible to keep data engine as standard version and install a enterprise version of analysis service?
Thank you very much
Tony
Yes. This is supported as in SQL Server 2005, Standardard SKU and Enterprise SKU can be installed side by side successfully. Of course, their instancenames must be distinct.
Can I implement replication between MS SQL Server Enterprise Edition and MSDE?
Hello.
One of our customers has requested that he wants to have data on his PC and
synchronize his data as needed.
How can I implement this?
Is it possible to synchronize data between MS SQL Server and MSDE?
Or is there any other solution?
Any advice or hint would be appreciated.AFAIR, yes. But you cannot have the MSDE as replication publisher.
Best regards,
Benny
"Kim Keuk Tae" <seiyanotenshi@.hotmail.com> skrev i en meddelelse
news:OADOIg$sDHA.2004@.TK2MSFTNGP10.phx.gbl...
> Hello.
> One of our customers has requested that he wants to have data on his PC
and
> synchronize his data as needed.
> How can I implement this?
> Is it possible to synchronize data between MS SQL Server and MSDE?
> Or is there any other solution?
> Any advice or hint would be appreciated.
>
>|||"Kim Keuk Tae" <seiyanotenshi@.hotmail.com> wrote in message
news:OADOIg$sDHA.2004@.TK2MSFTNGP10.phx.gbl...
> Hello.
> One of our customers has requested that he wants to have data on his PC
and
> synchronize his data as needed.
> How can I implement this?
> Is it possible to synchronize data between MS SQL Server and MSDE?
Hello, it is possible but not all replication types are available. I suggest
you follow this link:
http://msdn.microsoft.com/vstudio/downloads/addins/msde/examining.aspx
Regards,
Tomislav Kralj
MCSD/.NET, MCDBA
tomislav.kralj1@.zg.tel.hrsql
One of our customers has requested that he wants to have data on his PC and
synchronize his data as needed.
How can I implement this?
Is it possible to synchronize data between MS SQL Server and MSDE?
Or is there any other solution?
Any advice or hint would be appreciated.AFAIR, yes. But you cannot have the MSDE as replication publisher.
Best regards,
Benny
"Kim Keuk Tae" <seiyanotenshi@.hotmail.com> skrev i en meddelelse
news:OADOIg$sDHA.2004@.TK2MSFTNGP10.phx.gbl...
> Hello.
> One of our customers has requested that he wants to have data on his PC
and
> synchronize his data as needed.
> How can I implement this?
> Is it possible to synchronize data between MS SQL Server and MSDE?
> Or is there any other solution?
> Any advice or hint would be appreciated.
>
>|||"Kim Keuk Tae" <seiyanotenshi@.hotmail.com> wrote in message
news:OADOIg$sDHA.2004@.TK2MSFTNGP10.phx.gbl...
> Hello.
> One of our customers has requested that he wants to have data on his PC
and
> synchronize his data as needed.
> How can I implement this?
> Is it possible to synchronize data between MS SQL Server and MSDE?
Hello, it is possible but not all replication types are available. I suggest
you follow this link:
http://msdn.microsoft.com/vstudio/downloads/addins/msde/examining.aspx
Regards,
Tomislav Kralj
MCSD/.NET, MCDBA
tomislav.kralj1@.zg.tel.hrsql
Can I hide system objects in QA like in EM
...using SQL SERVER 2k
I know how to hide system objects in Enterprise Manager, but can this same
sort of thing be done in Query Analyzer... like what I see done on the Server
tab of Visual Studio?
thanks
kevin
No, that functionality is not available in QA. All you have is the pre-defined folders for user
tables and system tables. No such for stored procedures, but I hope that you don't have user
procedures in master? :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"kevin" <kevin@.discussions.microsoft.com> wrote in message
news:56016547-01C2-4E59-9F6B-5FD784744711@.microsoft.com...
> ...using SQL SERVER 2k
> I know how to hide system objects in Enterprise Manager, but can this same
> sort of thing be done in Query Analyzer... like what I see done on the Server
> tab of Visual Studio?
> thanks
> kevin
|||"Tibor Karaszi" wrote:
> No, that functionality is not available in QA. All you have is the pre-defined folders for user
> tables and system tables. No such for stored procedures, but I hope that you don't have user
> procedures in master? :-)
No, of course not. And I am not referring to the master, model, etc database.
In Enterprise Manager, in user created databases there are a number of SPs,
tables and views that are hidden if you select to hide system objects.
Obviously SQL SERVER/EM is intelligent enough to recognize the difference,
but Query Analyzer doesn't seem to be able to. Even users restricted to a
single DB can see master in QA.
It leads to a lot of scrolling to get to that one SP.
thanks
kevin
|||I see what you mean.
QA:
Tables:
These are already in separate folders, right?
Procedures:
You can delete the dt_ procedures, but they will come back when anyone uses EM to create diagram
etc.
Views:
The three system views will always be shown.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"kevin" <kevin@.discussions.microsoft.com> wrote in message
news:7BC4ED53-51A9-441C-BA8F-F5318B56FE7B@.microsoft.com...
> "Tibor Karaszi" wrote:
>
> No, of course not. And I am not referring to the master, model, etc database.
> In Enterprise Manager, in user created databases there are a number of SPs,
> tables and views that are hidden if you select to hide system objects.
> Obviously SQL SERVER/EM is intelligent enough to recognize the difference,
> but Query Analyzer doesn't seem to be able to. Even users restricted to a
> single DB can see master in QA.
> It leads to a lot of scrolling to get to that one SP.
> thanks
> kevin
|||Ah!!! Now you see. Its only the SP's that are a pain... honestly my middle
finger is cramping from all this damn scrolling. I just have to increase the
number of lines the scroll button moves with the mouse setup.
peace
kevin
"Tibor Karaszi" wrote:
> I see what you mean.
> QA:
> Tables:
> These are already in separate folders, right?
> Procedures:
> You can delete the dt_ procedures, but they will come back when anyone uses EM to create diagram
> etc.
> Views:
> The three system views will always be shown.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "kevin" <kevin@.discussions.microsoft.com> wrote in message
> news:7BC4ED53-51A9-441C-BA8F-F5318B56FE7B@.microsoft.com...
>
>
I know how to hide system objects in Enterprise Manager, but can this same
sort of thing be done in Query Analyzer... like what I see done on the Server
tab of Visual Studio?
thanks
kevin
No, that functionality is not available in QA. All you have is the pre-defined folders for user
tables and system tables. No such for stored procedures, but I hope that you don't have user
procedures in master? :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"kevin" <kevin@.discussions.microsoft.com> wrote in message
news:56016547-01C2-4E59-9F6B-5FD784744711@.microsoft.com...
> ...using SQL SERVER 2k
> I know how to hide system objects in Enterprise Manager, but can this same
> sort of thing be done in Query Analyzer... like what I see done on the Server
> tab of Visual Studio?
> thanks
> kevin
|||"Tibor Karaszi" wrote:
> No, that functionality is not available in QA. All you have is the pre-defined folders for user
> tables and system tables. No such for stored procedures, but I hope that you don't have user
> procedures in master? :-)
No, of course not. And I am not referring to the master, model, etc database.
In Enterprise Manager, in user created databases there are a number of SPs,
tables and views that are hidden if you select to hide system objects.
Obviously SQL SERVER/EM is intelligent enough to recognize the difference,
but Query Analyzer doesn't seem to be able to. Even users restricted to a
single DB can see master in QA.
It leads to a lot of scrolling to get to that one SP.
thanks
kevin
|||I see what you mean.
QA:
Tables:
These are already in separate folders, right?
Procedures:
You can delete the dt_ procedures, but they will come back when anyone uses EM to create diagram
etc.
Views:
The three system views will always be shown.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"kevin" <kevin@.discussions.microsoft.com> wrote in message
news:7BC4ED53-51A9-441C-BA8F-F5318B56FE7B@.microsoft.com...
> "Tibor Karaszi" wrote:
>
> No, of course not. And I am not referring to the master, model, etc database.
> In Enterprise Manager, in user created databases there are a number of SPs,
> tables and views that are hidden if you select to hide system objects.
> Obviously SQL SERVER/EM is intelligent enough to recognize the difference,
> but Query Analyzer doesn't seem to be able to. Even users restricted to a
> single DB can see master in QA.
> It leads to a lot of scrolling to get to that one SP.
> thanks
> kevin
|||Ah!!! Now you see. Its only the SP's that are a pain... honestly my middle
finger is cramping from all this damn scrolling. I just have to increase the
number of lines the scroll button moves with the mouse setup.
peace
kevin
"Tibor Karaszi" wrote:
> I see what you mean.
> QA:
> Tables:
> These are already in separate folders, right?
> Procedures:
> You can delete the dt_ procedures, but they will come back when anyone uses EM to create diagram
> etc.
> Views:
> The three system views will always be shown.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "kevin" <kevin@.discussions.microsoft.com> wrote in message
> news:7BC4ED53-51A9-441C-BA8F-F5318B56FE7B@.microsoft.com...
>
>
Can I have different SQL clients co-exist?
Can I have both SQL 6.5 client (Enterprise Manager, ISQL_w etc) and SQL 2000
(Enterprise Manager, SQL Analyzer) installed on the same machine?
Ippy wrote:
> Can I have both SQL 6.5 client (Enterprise Manager, ISQL_w etc) and
> SQL 2000 (Enterprise Manager, SQL Analyzer) installed on the same
> machine?
I don't believe that is supported. You can do what you want using a tool
like VirtualPC from Microsoft or VMWare. That is, you can run a virtual
PC and install whatever you want and have the virtual session connect
with your main PC or other PCs on your network.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Hi
It is possible and usable, but due to the fact that SQL Server 6.5 is no
longer supported by Microsoft, and Service Packs and hotfixes for SQL Server
2000 you may apply might break it.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ippy" <Ippy@.discussions.microsoft.com> wrote in message
news:857A42FB-1367-4278-A23E-4219812D495E@.microsoft.com...
> Can I have both SQL 6.5 client (Enterprise Manager, ISQL_w etc) and SQL
> 2000
> (Enterprise Manager, SQL Analyzer) installed on the same machine?
|||Hi,
Yes, you install SQL 6.5 and SQL 2000 in same machine. As well as you can
execute ISQLW and Enterprise manager of both versions in parallel.
Note:
If you are installing SQL 2000 client in a machine with SQL 7 client, the
SQL 2000 setup program will overwrite your SQL 7 client tools.
But SQL 2000 client tools support all SQL 7 activities.
Thanks
Hari
SQL Server MVP
"Ippy" <Ippy@.discussions.microsoft.com> wrote in message
news:857A42FB-1367-4278-A23E-4219812D495E@.microsoft.com...
> Can I have both SQL 6.5 client (Enterprise Manager, ISQL_w etc) and SQL
> 2000
> (Enterprise Manager, SQL Analyzer) installed on the same machine?
sql
(Enterprise Manager, SQL Analyzer) installed on the same machine?
Ippy wrote:
> Can I have both SQL 6.5 client (Enterprise Manager, ISQL_w etc) and
> SQL 2000 (Enterprise Manager, SQL Analyzer) installed on the same
> machine?
I don't believe that is supported. You can do what you want using a tool
like VirtualPC from Microsoft or VMWare. That is, you can run a virtual
PC and install whatever you want and have the virtual session connect
with your main PC or other PCs on your network.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Hi
It is possible and usable, but due to the fact that SQL Server 6.5 is no
longer supported by Microsoft, and Service Packs and hotfixes for SQL Server
2000 you may apply might break it.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ippy" <Ippy@.discussions.microsoft.com> wrote in message
news:857A42FB-1367-4278-A23E-4219812D495E@.microsoft.com...
> Can I have both SQL 6.5 client (Enterprise Manager, ISQL_w etc) and SQL
> 2000
> (Enterprise Manager, SQL Analyzer) installed on the same machine?
|||Hi,
Yes, you install SQL 6.5 and SQL 2000 in same machine. As well as you can
execute ISQLW and Enterprise manager of both versions in parallel.
Note:
If you are installing SQL 2000 client in a machine with SQL 7 client, the
SQL 2000 setup program will overwrite your SQL 7 client tools.
But SQL 2000 client tools support all SQL 7 activities.
Thanks
Hari
SQL Server MVP
"Ippy" <Ippy@.discussions.microsoft.com> wrote in message
news:857A42FB-1367-4278-A23E-4219812D495E@.microsoft.com...
> Can I have both SQL 6.5 client (Enterprise Manager, ISQL_w etc) and SQL
> 2000
> (Enterprise Manager, SQL Analyzer) installed on the same machine?
sql
Sunday, March 25, 2012
Can i execute stored procedure from enterprise manager
Can i execute stored procedure from enterprise manager?
ThanksI would of initially said no... but where there's a will there's a way.
you could always right click on a table, show top whatever rows, and show the SQL Query, in there try typing the "exec procname" statement. That should work. But if i were you, I'd stick with Query Analyzer.|||For what purpose?
ThanksI would of initially said no... but where there's a will there's a way.
you could always right click on a table, show top whatever rows, and show the SQL Query, in there try typing the "exec procname" statement. That should work. But if i were you, I'd stick with Query Analyzer.|||For what purpose?
Can I download the Enterprise Manager for SQL Server?
Hi,
I was wondering if I could download the Enterprise Manager for SQL Server. I am aware of some 3rd party tools but I want to use what comes w/ SQL Server.Enterprise Manager comes on the SQL Server installation disk. There is no separate download that I'm aware of (someone please correct me if I'm wrong).|||I dont believe its downloadable.
Its one of the things thats intentionally missing from MSDE.|||You may find this useful
SQL Server Web Data Administrator
It's a web based administration tool made by MS. It's free. I didn't try it though.|||www.outpost.com
search for sql server
get your credit card out
type in the info.
wait.
then install what they send to you.|||You can get developer version if not required for commercial purpose at low cost
can I download enterprise manager?
Can anyone tell me if it's possible to download SQL
Enterprise Manager to install on WinXP pro
I need it to connect to an SQL server database on a
webserver, and want to avoid the 267MB trial download.
Thanks for any info
dANEM is part of SQL Client Tools.
Locate your SQL Server CD and run Setup, choose Custom install and select
Client Tools Only.
This will install EM.
--
HTH
Ryan Waight, MCDBA, MCSE
"dAN" <dan@.monomen.co.uk> wrote in message
news:0ed101c393f6$78c09230$a401280a@.phx.gbl...
> Can anyone tell me if it's possible to download SQL
> Enterprise Manager to install on WinXP pro
> I need it to connect to an SQL server database on a
> webserver, and want to avoid the 267MB trial download.
> Thanks for any info
> dANsql
Enterprise Manager to install on WinXP pro
I need it to connect to an SQL server database on a
webserver, and want to avoid the 267MB trial download.
Thanks for any info
dANEM is part of SQL Client Tools.
Locate your SQL Server CD and run Setup, choose Custom install and select
Client Tools Only.
This will install EM.
--
HTH
Ryan Waight, MCDBA, MCSE
"dAN" <dan@.monomen.co.uk> wrote in message
news:0ed101c393f6$78c09230$a401280a@.phx.gbl...
> Can anyone tell me if it's possible to download SQL
> Enterprise Manager to install on WinXP pro
> I need it to connect to an SQL server database on a
> webserver, and want to avoid the 267MB trial download.
> Thanks for any info
> dANsql
Can I distribute MSDE 2000 with visual Studio 6.0 Enterprise Editi
Hello,
I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
Server Developer Edition bundeled with it:
- Do I have the right to use and distribute MSDE 2000?
- Do I have the right to upgrade to SQL 2000 server? If so, which version
of SQL 2000 Server I can upgrade to and how can I get it?
- Do I have the right to upgrade to Visual Studio.NET. If so, which version
of visual studio.Net I can upgrade to and how can I get it?
--
SalahAnytime you area dealing with licensing issues, you should always consult
your local Microsoft representation for an official answer. With that
disclaimer in mind, here's how I might answer you questions:
Yes...MSDE is the free, redistributable version of SQL Server. See the
following for more information
http://www.microsoft.com/sql/msde/default.mspx
[vbcol=seagreen]
Assuming that you've purchased a licensed version of one of the SQL Server
2000 Server editions, then yes, you may freely upgrade you databases to this
version. As to which version is right for you, that depends on what features
you need. Here's a matrix that may help you decide
http://www.microsoft.com/sql/evalua.../choosing.mspx.
[vbcol=seagreen]
Like SQL Server, assuming that you've purchased a licensed version of Visual
Studio.NET, then yes, you are free to upgrade you application. Also like my
answer for choosing a SQL Server version, choosing a version of Visual
Studio.NET depends on what features you need. The following URL may help
you decide
http://msdn.microsoft.com/vstudio/p...s/default.aspx.
--Brian
(Please reply to the newsgroups only.)
"Salah" <Salah@.discussions.microsoft.com> wrote in message
news:625F0DAD-EB9D-4831-9A66-A6366815AB86@.microsoft.com...[vbcol=seagreen]
> Hello,
> I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
> Server Developer Edition bundeled with it:
> - Do I have the right to use and distribute MSDE 2000?
> - Do I have the right to upgrade to SQL 2000 server? If so, which version
> of SQL 2000 Server I can upgrade to and how can I get it?
> - Do I have the right to upgrade to Visual Studio.NET. If so, which
> version
> of visual studio.Net I can upgrade to and how can I get it?
> --
> Salah
I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
Server Developer Edition bundeled with it:
- Do I have the right to use and distribute MSDE 2000?
- Do I have the right to upgrade to SQL 2000 server? If so, which version
of SQL 2000 Server I can upgrade to and how can I get it?
- Do I have the right to upgrade to Visual Studio.NET. If so, which version
of visual studio.Net I can upgrade to and how can I get it?
--
SalahAnytime you area dealing with licensing issues, you should always consult
your local Microsoft representation for an official answer. With that
disclaimer in mind, here's how I might answer you questions:
Yes...MSDE is the free, redistributable version of SQL Server. See the
following for more information
http://www.microsoft.com/sql/msde/default.mspx
[vbcol=seagreen]
Assuming that you've purchased a licensed version of one of the SQL Server
2000 Server editions, then yes, you may freely upgrade you databases to this
version. As to which version is right for you, that depends on what features
you need. Here's a matrix that may help you decide
http://www.microsoft.com/sql/evalua.../choosing.mspx.
[vbcol=seagreen]
Like SQL Server, assuming that you've purchased a licensed version of Visual
Studio.NET, then yes, you are free to upgrade you application. Also like my
answer for choosing a SQL Server version, choosing a version of Visual
Studio.NET depends on what features you need. The following URL may help
you decide
http://msdn.microsoft.com/vstudio/p...s/default.aspx.
--Brian
(Please reply to the newsgroups only.)
"Salah" <Salah@.discussions.microsoft.com> wrote in message
news:625F0DAD-EB9D-4831-9A66-A6366815AB86@.microsoft.com...[vbcol=seagreen]
> Hello,
> I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
> Server Developer Edition bundeled with it:
> - Do I have the right to use and distribute MSDE 2000?
> - Do I have the right to upgrade to SQL 2000 server? If so, which version
> of SQL 2000 Server I can upgrade to and how can I get it?
> - Do I have the right to upgrade to Visual Studio.NET. If so, which
> version
> of visual studio.Net I can upgrade to and how can I get it?
> --
> Salah
Can I distribute MSDE 2000 with visual Studio 6.0 Enterprise Editi
Hello,
I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
Server Developer Edition bundeled with it:
- Do I have the right to use and distribute MSDE 2000?
- Do I have the right to upgrade to SQL 2000 server? If so, which version
of SQL 2000 Server I can upgrade to and how can I get it?
- Do I have the right to upgrade to Visual Studio.NET. If so, which version
of visual studio.Net I can upgrade to and how can I get it?
Salah
Anytime you area dealing with licensing issues, you should always consult
your local Microsoft representation for an official answer. With that
disclaimer in mind, here's how I might answer you questions:
[vbcol=seagreen]
Yes...MSDE is the free, redistributable version of SQL Server. See the
following for more information
http://www.microsoft.com/sql/msde/default.mspx
[vbcol=seagreen]
Assuming that you've purchased a licensed version of one of the SQL Server
2000 Server editions, then yes, you may freely upgrade you databases to this
version. As to which version is right for you, that depends on what features
you need. Here's a matrix that may help you decide
http://www.microsoft.com/sql/evaluat...choosing.mspx.
[vbcol=seagreen]
Like SQL Server, assuming that you've purchased a licensed version of Visual
Studio.NET, then yes, you are free to upgrade you application. Also like my
answer for choosing a SQL Server version, choosing a version of Visual
Studio.NET depends on what features you need. The following URL may help
you decide
http://msdn.microsoft.com/vstudio/pr.../default.aspx.
--Brian
(Please reply to the newsgroups only.)
"Salah" <Salah@.discussions.microsoft.com> wrote in message
news:625F0DAD-EB9D-4831-9A66-A6366815AB86@.microsoft.com...
> Hello,
> I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
> Server Developer Edition bundeled with it:
> - Do I have the right to use and distribute MSDE 2000?
> - Do I have the right to upgrade to SQL 2000 server? If so, which version
> of SQL 2000 Server I can upgrade to and how can I get it?
> - Do I have the right to upgrade to Visual Studio.NET. If so, which
> version
> of visual studio.Net I can upgrade to and how can I get it?
> --
> Salah
I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
Server Developer Edition bundeled with it:
- Do I have the right to use and distribute MSDE 2000?
- Do I have the right to upgrade to SQL 2000 server? If so, which version
of SQL 2000 Server I can upgrade to and how can I get it?
- Do I have the right to upgrade to Visual Studio.NET. If so, which version
of visual studio.Net I can upgrade to and how can I get it?
Salah
Anytime you area dealing with licensing issues, you should always consult
your local Microsoft representation for an official answer. With that
disclaimer in mind, here's how I might answer you questions:
[vbcol=seagreen]
Yes...MSDE is the free, redistributable version of SQL Server. See the
following for more information
http://www.microsoft.com/sql/msde/default.mspx
[vbcol=seagreen]
Assuming that you've purchased a licensed version of one of the SQL Server
2000 Server editions, then yes, you may freely upgrade you databases to this
version. As to which version is right for you, that depends on what features
you need. Here's a matrix that may help you decide
http://www.microsoft.com/sql/evaluat...choosing.mspx.
[vbcol=seagreen]
Like SQL Server, assuming that you've purchased a licensed version of Visual
Studio.NET, then yes, you are free to upgrade you application. Also like my
answer for choosing a SQL Server version, choosing a version of Visual
Studio.NET depends on what features you need. The following URL may help
you decide
http://msdn.microsoft.com/vstudio/pr.../default.aspx.
--Brian
(Please reply to the newsgroups only.)
"Salah" <Salah@.discussions.microsoft.com> wrote in message
news:625F0DAD-EB9D-4831-9A66-A6366815AB86@.microsoft.com...
> Hello,
> I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
> Server Developer Edition bundeled with it:
> - Do I have the right to use and distribute MSDE 2000?
> - Do I have the right to upgrade to SQL 2000 server? If so, which version
> of SQL 2000 Server I can upgrade to and how can I get it?
> - Do I have the right to upgrade to Visual Studio.NET. If so, which
> version
> of visual studio.Net I can upgrade to and how can I get it?
> --
> Salah
Can I distribute MSDE 2000 with visual Studio 6.0 Enterprise Editi
Hello,
I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
Server Developer Edition bundeled with it:
- Do I have the right to use and distribute MSDE 2000?
- Do I have the right to upgrade to SQL 2000 server? If so, which version
of SQL 2000 Server I can upgrade to and how can I get it?
- Do I have the right to upgrade to Visual Studio.NET. If so, which version
of visual studio.Net I can upgrade to and how can I get it?
--
SalahAnytime you area dealing with licensing issues, you should always consult
your local Microsoft representation for an official answer. With that
disclaimer in mind, here's how I might answer you questions:
>>Do I have the right to use and distribute MSDE 2000?
Yes...MSDE is the free, redistributable version of SQL Server. See the
following for more information
http://www.microsoft.com/sql/msde/default.mspx
>>Do I have the right to upgrade to SQL 2000 server? If so, which version
>>of SQL 2000 Server I can upgrade to and how can I get it?
Assuming that you've purchased a licensed version of one of the SQL Server
2000 Server editions, then yes, you may freely upgrade you databases to this
version. As to which version is right for you, that depends on what features
you need. Here's a matrix that may help you decide
http://www.microsoft.com/sql/evaluation/features/choosing.mspx.
>>Do I have the right to upgrade to Visual Studio.NET. If so, which version
>>of visual studio.Net I can upgrade to and how can I get it?
Like SQL Server, assuming that you've purchased a licensed version of Visual
Studio.NET, then yes, you are free to upgrade you application. Also like my
answer for choosing a SQL Server version, choosing a version of Visual
Studio.NET depends on what features you need. The following URL may help
you decide
http://msdn.microsoft.com/vstudio/productinfo/features/default.aspx.
--
--Brian
(Please reply to the newsgroups only.)
"Salah" <Salah@.discussions.microsoft.com> wrote in message
news:625F0DAD-EB9D-4831-9A66-A6366815AB86@.microsoft.com...
> Hello,
> I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
> Server Developer Edition bundeled with it:
> - Do I have the right to use and distribute MSDE 2000?
> - Do I have the right to upgrade to SQL 2000 server? If so, which version
> of SQL 2000 Server I can upgrade to and how can I get it?
> - Do I have the right to upgrade to Visual Studio.NET. If so, which
> version
> of visual studio.Net I can upgrade to and how can I get it?
> --
> Salahsql
I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
Server Developer Edition bundeled with it:
- Do I have the right to use and distribute MSDE 2000?
- Do I have the right to upgrade to SQL 2000 server? If so, which version
of SQL 2000 Server I can upgrade to and how can I get it?
- Do I have the right to upgrade to Visual Studio.NET. If so, which version
of visual studio.Net I can upgrade to and how can I get it?
--
SalahAnytime you area dealing with licensing issues, you should always consult
your local Microsoft representation for an official answer. With that
disclaimer in mind, here's how I might answer you questions:
>>Do I have the right to use and distribute MSDE 2000?
Yes...MSDE is the free, redistributable version of SQL Server. See the
following for more information
http://www.microsoft.com/sql/msde/default.mspx
>>Do I have the right to upgrade to SQL 2000 server? If so, which version
>>of SQL 2000 Server I can upgrade to and how can I get it?
Assuming that you've purchased a licensed version of one of the SQL Server
2000 Server editions, then yes, you may freely upgrade you databases to this
version. As to which version is right for you, that depends on what features
you need. Here's a matrix that may help you decide
http://www.microsoft.com/sql/evaluation/features/choosing.mspx.
>>Do I have the right to upgrade to Visual Studio.NET. If so, which version
>>of visual studio.Net I can upgrade to and how can I get it?
Like SQL Server, assuming that you've purchased a licensed version of Visual
Studio.NET, then yes, you are free to upgrade you application. Also like my
answer for choosing a SQL Server version, choosing a version of Visual
Studio.NET depends on what features you need. The following URL may help
you decide
http://msdn.microsoft.com/vstudio/productinfo/features/default.aspx.
--
--Brian
(Please reply to the newsgroups only.)
"Salah" <Salah@.discussions.microsoft.com> wrote in message
news:625F0DAD-EB9D-4831-9A66-A6366815AB86@.microsoft.com...
> Hello,
> I have purchased Visual Studio 6.0 Enterprise Edition which has SQL 6.5
> Server Developer Edition bundeled with it:
> - Do I have the right to use and distribute MSDE 2000?
> - Do I have the right to upgrade to SQL 2000 server? If so, which version
> of SQL 2000 Server I can upgrade to and how can I get it?
> - Do I have the right to upgrade to Visual Studio.NET. If so, which
> version
> of visual studio.Net I can upgrade to and how can I get it?
> --
> Salahsql
Tuesday, March 20, 2012
Can I connect to MSDE through Enterprise Manager from another mach
Can I connect to MSDE through Enterprise Manager from another machine?
Yes you can. Register it with EM just like you would any other SQL Server
instance.
Jim
"lanem" <lanem@.discussions.microsoft.com> wrote in message
news:FABE36D6-5B25-48FD-8620-EECD27067B8D@.microsoft.com...
> Can I connect to MSDE through Enterprise Manager from another machine?
sql
Yes you can. Register it with EM just like you would any other SQL Server
instance.
Jim
"lanem" <lanem@.discussions.microsoft.com> wrote in message
news:FABE36D6-5B25-48FD-8620-EECD27067B8D@.microsoft.com...
> Can I connect to MSDE through Enterprise Manager from another machine?
sql
Can I connect SQL Enterprise Manager ...
To an internet address (ip).
Is this done by registering the "IP" instead of the server name?
Many thanks
MP
You can use the IP address instead of the server name. Just try 127.0.0.1 to
connect to your local server. If you think the ip addresses are confusing in
Enterprise Manager, you can use the Client Network Utility to set up an
alias that you can use instead.
Jacco Schalkwijk
SQL Server MVP
"Michael Persaud" <michaelsrpersaud@.hotmail.com> wrote in message
news:eG5W5bmeEHA.3944@.tk2msftngp13.phx.gbl...
> To an internet address (ip).
> Is this done by registering the "IP" instead of the server name?
> Many thanks
> MP
>
Is this done by registering the "IP" instead of the server name?
Many thanks
MP
You can use the IP address instead of the server name. Just try 127.0.0.1 to
connect to your local server. If you think the ip addresses are confusing in
Enterprise Manager, you can use the Client Network Utility to set up an
alias that you can use instead.
Jacco Schalkwijk
SQL Server MVP
"Michael Persaud" <michaelsrpersaud@.hotmail.com> wrote in message
news:eG5W5bmeEHA.3944@.tk2msftngp13.phx.gbl...
> To an internet address (ip).
> Is this done by registering the "IP" instead of the server name?
> Many thanks
> MP
>
Can I connect SQL Enterprise Manager ...
To an internet address (ip).
Is this done by registering the "IP" instead of the server name'
Many thanks
MPYou can use the IP address instead of the server name. Just try 127.0.0.1 to
connect to your local server. If you think the ip addresses are confusing in
Enterprise Manager, you can use the Client Network Utility to set up an
alias that you can use instead.
Jacco Schalkwijk
SQL Server MVP
"Michael Persaud" <michaelsrpersaud@.hotmail.com> wrote in message
news:eG5W5bmeEHA.3944@.tk2msftngp13.phx.gbl...
> To an internet address (ip).
> Is this done by registering the "IP" instead of the server name'
> Many thanks
> MP
>
Is this done by registering the "IP" instead of the server name'
Many thanks
MPYou can use the IP address instead of the server name. Just try 127.0.0.1 to
connect to your local server. If you think the ip addresses are confusing in
Enterprise Manager, you can use the Client Network Utility to set up an
alias that you can use instead.
Jacco Schalkwijk
SQL Server MVP
"Michael Persaud" <michaelsrpersaud@.hotmail.com> wrote in message
news:eG5W5bmeEHA.3944@.tk2msftngp13.phx.gbl...
> To an internet address (ip).
> Is this done by registering the "IP" instead of the server name'
> Many thanks
> MP
>
Sunday, March 11, 2012
Can Enterprise Evalution Edition be installed on Windows XP SP2 Home Edition now?
Thanks.
I don't believe so, enterprise edition required advanced server.
You can install developer edition which has the same functionality as enterprise edition.
|||? No. I believe that only Developer Edition and Express Edition can be installed on XP Home SP2. Developer Edition allows you to test the behavior of Enterprise Edition. Developer Edition is about $50 retail and is also available on MSDN (I'm not sure if all subscription levels include it). Andrew Watt [MVP] <msibm@.discussions.microsoft.com> wrote in message news:6b652bb3-2e4f-48b7-a192-fbe26a4ee9da@.discussions.microsoft.com... Thanks.Can I access MSDE on a remote machine with Enterprise Manager?
We just installed an application, WhatsUpGold, to monitor our servers. Management won't let me host that on my primary SQL box. So, we are using MSDE on the local machine (call that box my_netmon).
I can access the db with very basic functionality using osql while on the my_netmon machine. I've added my domain user account as a System Admin using the following commands.
exec sp_grantlogin @.name
go
exec sp_addsrvrolemember @.name, 'sysadmin'
But when I go to the my_sql machine and try to attach to it with Enterprise Manager I get an error that the server does not exist.
What gives? Is it just not possible, or am I missing something here?
My goal is to just be able to see the data stored in the MSDE db. Write views, etc...
Please advise,
MarcHas anybody accessed MSDE from a remote machine. Or can it only be access locally with ODBC type connections?|||yes, you can use MSDE remotely. what does your connection string look like? is it a named instance?
for that matter, why bother with MSDE? it's ancient. you should use SQL Server Express if this is for new development.
I can access the db with very basic functionality using osql while on the my_netmon machine. I've added my domain user account as a System Admin using the following commands.
exec sp_grantlogin @.name
go
exec sp_addsrvrolemember @.name, 'sysadmin'
But when I go to the my_sql machine and try to attach to it with Enterprise Manager I get an error that the server does not exist.
What gives? Is it just not possible, or am I missing something here?
My goal is to just be able to see the data stored in the MSDE db. Write views, etc...
Please advise,
MarcHas anybody accessed MSDE from a remote machine. Or can it only be access locally with ODBC type connections?|||yes, you can use MSDE remotely. what does your connection string look like? is it a named instance?
for that matter, why bother with MSDE? it's ancient. you should use SQL Server Express if this is for new development.
Thursday, March 8, 2012
can connect using sql query analyzer but not osql or isql
I have a SQL server 2000 enterprise edition installed on windows 2000
advanced server. It starts successfully and using SQL query analyzer, I can
connect to it using windows authentication and execute sql statements without
a problem.
But when I used isql (either just isql or isql [-U login id]), I got the
following error message:
Msg 18456, Level 14, State 1:
Login failed for user 'Administrator'.
DB-Library: Login incorrect.
If I use osql,
I got:
Login failed for user 'Administrator'.
Weirdly, NO logon information is recorded in ERRORLOG.
In SQL query analyzer, I used the login id Administrator, which is what I
used to login to Windows.
After installation of sql server, we changed the password of Windows
Administrator account, so there might be a password mismatch. But I can use
the new password
to connect to sql server in SQL query analyzer, but not osql or isql.
I tried osql and isql with both the new password and the old one(not sure if
it is correct), but neither of them worked.
What might be the cause?
Thank you very much,
I think you're confusing Windows authentication with SQL
authentication. When you try connecting with osql try the -E (trusted
login) parameter rather than -U Administrator. With Windows
authentication you don't specify a password as the windows security
token for your windows account is used instead (which has already been
authenticated by a domain controller).
*mike hodgson*
http://sqlnerd.blogspot.com
Tammy wrote:
>I have a SQL server 2000 enterprise edition installed on windows 2000
>advanced server. It starts successfully and using SQL query analyzer, I can
>connect to it using windows authentication and execute sql statements without
>a problem.
>But when I used isql (either just isql or isql [-U login id]), I got the
>following error message:
>Msg 18456, Level 14, State 1:
>Login failed for user 'Administrator'.
>DB-Library: Login incorrect.
>If I use osql,
>I got:
>Login failed for user 'Administrator'.
>Weirdly, NO logon information is recorded in ERRORLOG.
>In SQL query analyzer, I used the login id Administrator, which is what I
>used to login to Windows.
>After installation of sql server, we changed the password of Windows
>Administrator account, so there might be a password mismatch. But I can use
>the new password
>to connect to sql server in SQL query analyzer, but not osql or isql.
>I tried osql and isql with both the new password and the old one(not sure if
>it is correct), but neither of them worked.
>What might be the cause?
>Thank you very much,
>
>
|||It works! Thank you, Mike.
"Mike Hodgson" wrote:
> I think you're confusing Windows authentication with SQL
> authentication. When you try connecting with osql try the -E (trusted
> login) parameter rather than -U Administrator. With Windows
> authentication you don't specify a password as the windows security
> token for your windows account is used instead (which has already been
> authenticated by a domain controller).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Tammy wrote:
>
advanced server. It starts successfully and using SQL query analyzer, I can
connect to it using windows authentication and execute sql statements without
a problem.
But when I used isql (either just isql or isql [-U login id]), I got the
following error message:
Msg 18456, Level 14, State 1:
Login failed for user 'Administrator'.
DB-Library: Login incorrect.
If I use osql,
I got:
Login failed for user 'Administrator'.
Weirdly, NO logon information is recorded in ERRORLOG.
In SQL query analyzer, I used the login id Administrator, which is what I
used to login to Windows.
After installation of sql server, we changed the password of Windows
Administrator account, so there might be a password mismatch. But I can use
the new password
to connect to sql server in SQL query analyzer, but not osql or isql.
I tried osql and isql with both the new password and the old one(not sure if
it is correct), but neither of them worked.
What might be the cause?
Thank you very much,
I think you're confusing Windows authentication with SQL
authentication. When you try connecting with osql try the -E (trusted
login) parameter rather than -U Administrator. With Windows
authentication you don't specify a password as the windows security
token for your windows account is used instead (which has already been
authenticated by a domain controller).
*mike hodgson*
http://sqlnerd.blogspot.com
Tammy wrote:
>I have a SQL server 2000 enterprise edition installed on windows 2000
>advanced server. It starts successfully and using SQL query analyzer, I can
>connect to it using windows authentication and execute sql statements without
>a problem.
>But when I used isql (either just isql or isql [-U login id]), I got the
>following error message:
>Msg 18456, Level 14, State 1:
>Login failed for user 'Administrator'.
>DB-Library: Login incorrect.
>If I use osql,
>I got:
>Login failed for user 'Administrator'.
>Weirdly, NO logon information is recorded in ERRORLOG.
>In SQL query analyzer, I used the login id Administrator, which is what I
>used to login to Windows.
>After installation of sql server, we changed the password of Windows
>Administrator account, so there might be a password mismatch. But I can use
>the new password
>to connect to sql server in SQL query analyzer, but not osql or isql.
>I tried osql and isql with both the new password and the old one(not sure if
>it is correct), but neither of them worked.
>What might be the cause?
>Thank you very much,
>
>
|||It works! Thank you, Mike.
"Mike Hodgson" wrote:
> I think you're confusing Windows authentication with SQL
> authentication. When you try connecting with osql try the -E (trusted
> login) parameter rather than -U Administrator. With Windows
> authentication you don't specify a password as the windows security
> token for your windows account is used instead (which has already been
> authenticated by a domain controller).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Tammy wrote:
>
can connect using sql query analyzer but not osql or isql
I have a SQL server 2000 enterprise edition installed on windows 2000
advanced server. It starts successfully and using SQL query analyzer, I can
connect to it using windows authentication and execute sql statements withou
t
a problem.
But when I used isql (either just isql or isql [-U login id]), I got the
following error message:
Msg 18456, Level 14, State 1:
Login failed for user 'Administrator'.
DB-Library: Login incorrect.
If I use osql,
I got:
Login failed for user 'Administrator'.
Weirdly, NO logon information is recorded in ERRORLOG.
In SQL query analyzer, I used the login id Administrator, which is what I
used to login to Windows.
After installation of sql server, we changed the password of Windows
Administrator account, so there might be a password mismatch. But I can use
the new password
to connect to sql server in SQL query analyzer, but not osql or isql.
I tried osql and isql with both the new password and the old one(not sure if
it is correct), but neither of them worked.
What might be the cause?
Thank you very much,I think you're confusing Windows authentication with SQL
authentication. When you try connecting with osql try the -E (trusted
login) parameter rather than -U Administrator. With Windows
authentication you don't specify a password as the windows security
token for your windows account is used instead (which has already been
authenticated by a domain controller).
*mike hodgson*
http://sqlnerd.blogspot.com
Tammy wrote:
>I have a SQL server 2000 enterprise edition installed on windows 2000
>advanced server. It starts successfully and using SQL query analyzer, I can
>connect to it using windows authentication and execute sql statements witho
ut
>a problem.
>But when I used isql (either just isql or isql [-U login id]), I got th
e
>following error message:
>Msg 18456, Level 14, State 1:
>Login failed for user 'Administrator'.
>DB-Library: Login incorrect.
>If I use osql,
>I got:
>Login failed for user 'Administrator'.
>Weirdly, NO logon information is recorded in ERRORLOG.
>In SQL query analyzer, I used the login id Administrator, which is what I
>used to login to Windows.
>After installation of sql server, we changed the password of Windows
>Administrator account, so there might be a password mismatch. But I can use
>the new password
>to connect to sql server in SQL query analyzer, but not osql or isql.
>I tried osql and isql with both the new password and the old one(not sure i
f
>it is correct), but neither of them worked.
>What might be the cause?
>Thank you very much,
>
>|||It works! Thank you, Mike.
"Mike Hodgson" wrote:
> I think you're confusing Windows authentication with SQL
> authentication. When you try connecting with osql try the -E (trusted
> login) parameter rather than -U Administrator. With Windows
> authentication you don't specify a password as the windows security
> token for your windows account is used instead (which has already been
> authenticated by a domain controller).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Tammy wrote:
>
>
advanced server. It starts successfully and using SQL query analyzer, I can
connect to it using windows authentication and execute sql statements withou
t
a problem.
But when I used isql (either just isql or isql [-U login id]), I got the
following error message:
Msg 18456, Level 14, State 1:
Login failed for user 'Administrator'.
DB-Library: Login incorrect.
If I use osql,
I got:
Login failed for user 'Administrator'.
Weirdly, NO logon information is recorded in ERRORLOG.
In SQL query analyzer, I used the login id Administrator, which is what I
used to login to Windows.
After installation of sql server, we changed the password of Windows
Administrator account, so there might be a password mismatch. But I can use
the new password
to connect to sql server in SQL query analyzer, but not osql or isql.
I tried osql and isql with both the new password and the old one(not sure if
it is correct), but neither of them worked.
What might be the cause?
Thank you very much,I think you're confusing Windows authentication with SQL
authentication. When you try connecting with osql try the -E (trusted
login) parameter rather than -U Administrator. With Windows
authentication you don't specify a password as the windows security
token for your windows account is used instead (which has already been
authenticated by a domain controller).
*mike hodgson*
http://sqlnerd.blogspot.com
Tammy wrote:
>I have a SQL server 2000 enterprise edition installed on windows 2000
>advanced server. It starts successfully and using SQL query analyzer, I can
>connect to it using windows authentication and execute sql statements witho
ut
>a problem.
>But when I used isql (either just isql or isql [-U login id]), I got th
e
>following error message:
>Msg 18456, Level 14, State 1:
>Login failed for user 'Administrator'.
>DB-Library: Login incorrect.
>If I use osql,
>I got:
>Login failed for user 'Administrator'.
>Weirdly, NO logon information is recorded in ERRORLOG.
>In SQL query analyzer, I used the login id Administrator, which is what I
>used to login to Windows.
>After installation of sql server, we changed the password of Windows
>Administrator account, so there might be a password mismatch. But I can use
>the new password
>to connect to sql server in SQL query analyzer, but not osql or isql.
>I tried osql and isql with both the new password and the old one(not sure i
f
>it is correct), but neither of them worked.
>What might be the cause?
>Thank you very much,
>
>|||It works! Thank you, Mike.
"Mike Hodgson" wrote:
> I think you're confusing Windows authentication with SQL
> authentication. When you try connecting with osql try the -E (trusted
> login) parameter rather than -U Administrator. With Windows
> authentication you don't specify a password as the windows security
> token for your windows account is used instead (which has already been
> authenticated by a domain controller).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Tammy wrote:
>
>
can connect using sql query analyzer but not osql or isql
I have a SQL server 2000 enterprise edition installed on windows 2000
advanced server. It starts successfully and using SQL query analyzer, I can
connect to it using windows authentication and execute sql statements without
a problem.
But when I used isql (either just isql or isql [-U login id]), I got the
following error message:
Msg 18456, Level 14, State 1:
Login failed for user 'Administrator'.
DB-Library: Login incorrect.
If I use osql,
I got:
Login failed for user 'Administrator'.
Weirdly, NO logon information is recorded in ERRORLOG.
In SQL query analyzer, I used the login id Administrator, which is what I
used to login to Windows.
After installation of sql server, we changed the password of Windows
Administrator account, so there might be a password mismatch. But I can use
the new password
to connect to sql server in SQL query analyzer, but not osql or isql.
I tried osql and isql with both the new password and the old one(not sure if
it is correct), but neither of them worked.
What might be the cause?
Thank you very much,This is a multi-part message in MIME format.
--070107040706020904060707
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
I think you're confusing Windows authentication with SQL
authentication. When you try connecting with osql try the -E (trusted
login) parameter rather than -U Administrator. With Windows
authentication you don't specify a password as the windows security
token for your windows account is used instead (which has already been
authenticated by a domain controller).
--
*mike hodgson*
http://sqlnerd.blogspot.com
Tammy wrote:
>I have a SQL server 2000 enterprise edition installed on windows 2000
>advanced server. It starts successfully and using SQL query analyzer, I can
>connect to it using windows authentication and execute sql statements without
>a problem.
>But when I used isql (either just isql or isql [-U login id]), I got the
>following error message:
>Msg 18456, Level 14, State 1:
>Login failed for user 'Administrator'.
>DB-Library: Login incorrect.
>If I use osql,
>I got:
>Login failed for user 'Administrator'.
>Weirdly, NO logon information is recorded in ERRORLOG.
>In SQL query analyzer, I used the login id Administrator, which is what I
>used to login to Windows.
>After installation of sql server, we changed the password of Windows
>Administrator account, so there might be a password mismatch. But I can use
>the new password
>to connect to sql server in SQL query analyzer, but not osql or isql.
>I tried osql and isql with both the new password and the old one(not sure if
>it is correct), but neither of them worked.
>What might be the cause?
>Thank you very much,
>
>
--070107040706020904060707
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>I think you're confusing Windows authentication with SQL
authentication. When you try connecting with osql try the -E (trusted
login) parameter rather than -U Administrator. With Windows
authentication you don't specify a password as the windows security
token for your windows account is used instead (which has already been
authenticated by a domain controller).</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Tammy wrote:
<blockquote cite="mid2F4B9DBB-392C-4D73-B9E0-5709FE1E206F@.microsoft.com"
type="cite">
<pre wrap="">I have a SQL server 2000 enterprise edition installed on windows 2000
advanced server. It starts successfully and using SQL query analyzer, I can
connect to it using windows authentication and execute sql statements without
a problem.
But when I used isql (either just isql or isql [-U login id]), I got the
following error message:
Msg 18456, Level 14, State 1:
Login failed for user 'Administrator'.
DB-Library: Login incorrect.
If I use osql,
I got:
Login failed for user 'Administrator'.
Weirdly, NO logon information is recorded in ERRORLOG.
In SQL query analyzer, I used the login id Administrator, which is what I
used to login to Windows.
After installation of sql server, we changed the password of Windows
Administrator account, so there might be a password mismatch. But I can use
the new password
to connect to sql server in SQL query analyzer, but not osql or isql.
I tried osql and isql with both the new password and the old one(not sure if
it is correct), but neither of them worked.
What might be the cause?
Thank you very much,
</pre>
</blockquote>
</body>
</html>
--070107040706020904060707--|||It works! Thank you, Mike.
"Mike Hodgson" wrote:
> I think you're confusing Windows authentication with SQL
> authentication. When you try connecting with osql try the -E (trusted
> login) parameter rather than -U Administrator. With Windows
> authentication you don't specify a password as the windows security
> token for your windows account is used instead (which has already been
> authenticated by a domain controller).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Tammy wrote:
> >I have a SQL server 2000 enterprise edition installed on windows 2000
> >advanced server. It starts successfully and using SQL query analyzer, I can
> >connect to it using windows authentication and execute sql statements without
> >a problem.
> >
> >But when I used isql (either just isql or isql [-U login id]), I got the
> >following error message:
> >Msg 18456, Level 14, State 1:
> >Login failed for user 'Administrator'.
> >DB-Library: Login incorrect.
> >
> >If I use osql,
> >I got:
> >Login failed for user 'Administrator'.
> >
> >Weirdly, NO logon information is recorded in ERRORLOG.
> >
> >In SQL query analyzer, I used the login id Administrator, which is what I
> >used to login to Windows.
> >After installation of sql server, we changed the password of Windows
> >Administrator account, so there might be a password mismatch. But I can use
> >the new password
> >to connect to sql server in SQL query analyzer, but not osql or isql.
> >
> >I tried osql and isql with both the new password and the old one(not sure if
> >it is correct), but neither of them worked.
> >
> >What might be the cause?
> >
> >Thank you very much,
> >
> >
> >
>
advanced server. It starts successfully and using SQL query analyzer, I can
connect to it using windows authentication and execute sql statements without
a problem.
But when I used isql (either just isql or isql [-U login id]), I got the
following error message:
Msg 18456, Level 14, State 1:
Login failed for user 'Administrator'.
DB-Library: Login incorrect.
If I use osql,
I got:
Login failed for user 'Administrator'.
Weirdly, NO logon information is recorded in ERRORLOG.
In SQL query analyzer, I used the login id Administrator, which is what I
used to login to Windows.
After installation of sql server, we changed the password of Windows
Administrator account, so there might be a password mismatch. But I can use
the new password
to connect to sql server in SQL query analyzer, but not osql or isql.
I tried osql and isql with both the new password and the old one(not sure if
it is correct), but neither of them worked.
What might be the cause?
Thank you very much,This is a multi-part message in MIME format.
--070107040706020904060707
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
I think you're confusing Windows authentication with SQL
authentication. When you try connecting with osql try the -E (trusted
login) parameter rather than -U Administrator. With Windows
authentication you don't specify a password as the windows security
token for your windows account is used instead (which has already been
authenticated by a domain controller).
--
*mike hodgson*
http://sqlnerd.blogspot.com
Tammy wrote:
>I have a SQL server 2000 enterprise edition installed on windows 2000
>advanced server. It starts successfully and using SQL query analyzer, I can
>connect to it using windows authentication and execute sql statements without
>a problem.
>But when I used isql (either just isql or isql [-U login id]), I got the
>following error message:
>Msg 18456, Level 14, State 1:
>Login failed for user 'Administrator'.
>DB-Library: Login incorrect.
>If I use osql,
>I got:
>Login failed for user 'Administrator'.
>Weirdly, NO logon information is recorded in ERRORLOG.
>In SQL query analyzer, I used the login id Administrator, which is what I
>used to login to Windows.
>After installation of sql server, we changed the password of Windows
>Administrator account, so there might be a password mismatch. But I can use
>the new password
>to connect to sql server in SQL query analyzer, but not osql or isql.
>I tried osql and isql with both the new password and the old one(not sure if
>it is correct), but neither of them worked.
>What might be the cause?
>Thank you very much,
>
>
--070107040706020904060707
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>I think you're confusing Windows authentication with SQL
authentication. When you try connecting with osql try the -E (trusted
login) parameter rather than -U Administrator. With Windows
authentication you don't specify a password as the windows security
token for your windows account is used instead (which has already been
authenticated by a domain controller).</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Tammy wrote:
<blockquote cite="mid2F4B9DBB-392C-4D73-B9E0-5709FE1E206F@.microsoft.com"
type="cite">
<pre wrap="">I have a SQL server 2000 enterprise edition installed on windows 2000
advanced server. It starts successfully and using SQL query analyzer, I can
connect to it using windows authentication and execute sql statements without
a problem.
But when I used isql (either just isql or isql [-U login id]), I got the
following error message:
Msg 18456, Level 14, State 1:
Login failed for user 'Administrator'.
DB-Library: Login incorrect.
If I use osql,
I got:
Login failed for user 'Administrator'.
Weirdly, NO logon information is recorded in ERRORLOG.
In SQL query analyzer, I used the login id Administrator, which is what I
used to login to Windows.
After installation of sql server, we changed the password of Windows
Administrator account, so there might be a password mismatch. But I can use
the new password
to connect to sql server in SQL query analyzer, but not osql or isql.
I tried osql and isql with both the new password and the old one(not sure if
it is correct), but neither of them worked.
What might be the cause?
Thank you very much,
</pre>
</blockquote>
</body>
</html>
--070107040706020904060707--|||It works! Thank you, Mike.
"Mike Hodgson" wrote:
> I think you're confusing Windows authentication with SQL
> authentication. When you try connecting with osql try the -E (trusted
> login) parameter rather than -U Administrator. With Windows
> authentication you don't specify a password as the windows security
> token for your windows account is used instead (which has already been
> authenticated by a domain controller).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Tammy wrote:
> >I have a SQL server 2000 enterprise edition installed on windows 2000
> >advanced server. It starts successfully and using SQL query analyzer, I can
> >connect to it using windows authentication and execute sql statements without
> >a problem.
> >
> >But when I used isql (either just isql or isql [-U login id]), I got the
> >following error message:
> >Msg 18456, Level 14, State 1:
> >Login failed for user 'Administrator'.
> >DB-Library: Login incorrect.
> >
> >If I use osql,
> >I got:
> >Login failed for user 'Administrator'.
> >
> >Weirdly, NO logon information is recorded in ERRORLOG.
> >
> >In SQL query analyzer, I used the login id Administrator, which is what I
> >used to login to Windows.
> >After installation of sql server, we changed the password of Windows
> >Administrator account, so there might be a password mismatch. But I can use
> >the new password
> >to connect to sql server in SQL query analyzer, but not osql or isql.
> >
> >I tried osql and isql with both the new password and the old one(not sure if
> >it is correct), but neither of them worked.
> >
> >What might be the cause?
> >
> >Thank you very much,
> >
> >
> >
>
Subscribe to:
Posts (Atom)