Thursday, March 29, 2012
Can i install MS SQL Server in Novell 5
does anyone know if MS SQL SERVER 2000 can be installed on Novell 5, and if there are any challenges that need to be considered.
Thanks to all,
SammySQL Server installs only on Windoze. It works nicely in a Novell network, but it won't install on a Novell server.
-PatP|||thanks Pat, much appreciated
Can I have...
Hi
Is it possible to have both sql server 2005 and sql server express 2005 installed on the same machine?
thanks
Yes.
SQL Server Express will install with a 'default' instance name of [.\SQLExpress]
And if you allow the SQL (non-Express) to use the 'default' instance, it will be know by the computer name.
|||As long as you do not specify the non-SQLExpress instance to be the named "SQLEXPRESS" instance, you can install as many additional SQL Server non-SQLExpress instances in addition to the SQL Server Express one as the machine can take.
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Thanks guys.sqlCan I Have Link Between Several servers
hello all
I have a web application(asp.net) and Database(sql server 2005) .
we have installed them on several servers.
now we want to have a connection between apllication on one server to a database on another server .
for example we have Server(A) and Server(B) the DataBases and Web apllications on two server are the same.
sometimes the Apllication on server(A) must connect to database on server(B).
whats the solution plz?
note that the number of servers can be inceased in the future this mean the number of servers are not fixed.
thanks
Use the function sp_linkedServer of the SQL to link the borh servers.
helped?
Regards
Can I Have link Between Several Servers
hello all
I have a web application(asp.net) and Database(sql server 2005) .
we have installed them on several servers.
now we want to have a connection between apllication on one server to a database on another server .
for example we have Server(A) and Server(B) the DataBases and Web apllications on two server are the same.
sometimes the Apllication on server(A) must connect to database on server(B).
whats the solution plz?
note that the number of servers can be inceased in the future this mean the number of servers are not fixed.
thanks
Not sure I follow -- do you mean you have 2 different database serves that should mirror each other, ie, the data is the same and updates on one should be mirrored on the other?
|||
You have a database in the server A .. connect to it by using ConnectionStringA , and any need data from Server B .. use another ConnectionString (e.g. ConnectionStringB).
So, in the web.config file you will have tow ConnectionStrings (A & B).. when to connect to the database in the same server use StringConnectionA and the other used to connect to the database in the another server (server B) - called ConnectionString B.
Good luck.
|||thank you
for Contributor : i have defrerent data in each databas i cant use replication
for Participant : i must connect to different web server .
i get it that i must to use splinkserver to link servers
thanks forever.
Can I have different SQL clients co-exist?
(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 do rolling upgrade of active-active SQL cluster
We have an active-active cluster where SQL server instances are created on
node 1 and Analysis services are installed on node 2. We need to upgrade the
H/W for both nodes? Can I do a rolling upgrade i.e. replacing one node at
time in above configuration?
If not then what are my options & if yes then can you give me some links to
documentation on how to do this?
Thanks,
Sushil
Sushil
Yes you can. I have done exactly this type of project. The more you plan
and test, the better your chance of success. I don't have any publicly
available documentation on a rolling upgrade.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sushil" <Sushil@.discussions.microsoft.com> wrote in message
news:EA4D680F-4548-4536-8BD2-88ECE1004CF8@.microsoft.com...
> Hi,
> We have an active-active cluster where SQL server instances are created on
> node 1 and Analysis services are installed on node 2. We need to upgrade
> the
> H/W for both nodes? Can I do a rolling upgrade i.e. replacing one node at
> time in above configuration?
> If not then what are my options & if yes then can you give me some links
> to
> documentation on how to do this?
> Thanks,
> --
> Sushil
> --
> Sushil
|||Geoff,
Thanks for response. Can you please list if you had any challenges while
doing this?
I have been told that, When we replace node 2 by new node (Just with OS)
and install SQL server on this new node and try to cluster this new node
with OLD node 1 then that clustering will not work.
Can you point me any Microsoft documentation or books where I can get some
clues?
Thanks,
Sushil
Sushil
"Geoff N. Hiten" wrote:
> Yes you can. I have done exactly this type of project. The more you plan
> and test, the better your chance of success. I don't have any publicly
> available documentation on a rolling upgrade.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Sushil" <Sushil@.discussions.microsoft.com> wrote in message
> news:EA4D680F-4548-4536-8BD2-88ECE1004CF8@.microsoft.com...
>
>
|||Here is the quick version.
Starting with SQL 2000 2-node (4-Proc DELL) connected to DELL | EMC CX-600.
Windows 2000 OS. 2 SQL Instances.
Ended with SQL 2000 4-node (8-proc Unisys) still connected to the same SAN
(expanded the storage capacity, though). Windows 2003 OS. 3 SQL Instances.
Started with in-place upgrade of OS (one node at a time). Obtaining the
correct drivers for the HBAs was a challenge. This was Q4 '03, so that
shouldn't be a problem, but it is a critical step.
Added the two new nodes. When stable, removed original two nodes. Finally
added the remaining new nodes.
Note that if you have a SCSI based cluster, you cannot have more than two
nodes even with Windows 2003.
Again, planning and testing was essential. Each step had numerous tests and
bailout plans to avoid downtime.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sushil" <Sushil@.discussions.microsoft.com> wrote in message
news:97D3A989-1C04-450C-B3C4-20F674299E09@.microsoft.com...[vbcol=seagreen]
> Geoff,
> Thanks for response. Can you please list if you had any challenges while
> doing this?
> I have been told that, When we replace node 2 by new node (Just with OS)
> and install SQL server on this new node and try to cluster this new node
> with OLD node 1 then that clustering will not work.
> Can you point me any Microsoft documentation or books where I can get some
> clues?
> Thanks,
> Sushil
>
> --
> Sushil
>
> "Geoff N. Hiten" wrote:
|||I have a thought rolling around in my brain about limitations of the number
of nodes being different between WIn2K and Win2K3...but I can't remember the
specifics. Geoff, can you recall or am I off-base (anymore than usual?)
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.expertsrt.com - not your average tech Q&A site
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OF3pKh0MGHA.4052@.TK2MSFTNGP15.phx.gbl...
> Here is the quick version.
> Starting with SQL 2000 2-node (4-Proc DELL) connected to DELL | EMC
> CX-600. Windows 2000 OS. 2 SQL Instances.
> Ended with SQL 2000 4-node (8-proc Unisys) still connected to the same SAN
> (expanded the storage capacity, though). Windows 2003 OS. 3 SQL
> Instances.
> Started with in-place upgrade of OS (one node at a time). Obtaining the
> correct drivers for the HBAs was a challenge. This was Q4 '03, so that
> shouldn't be a problem, but it is a critical step.
> Added the two new nodes. When stable, removed original two nodes.
> Finally added the remaining new nodes.
> Note that if you have a SCSI based cluster, you cannot have more than two
> nodes even with Windows 2003.
> Again, planning and testing was essential. Each step had numerous tests
> and bailout plans to avoid downtime.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Sushil" <Sushil@.discussions.microsoft.com> wrote in message
> news:97D3A989-1C04-450C-B3C4-20F674299E09@.microsoft.com...
>
|||Windows 2000 Enterprise Edition supports 2 nodes. Windows 2003 supports up
to 8 nodes, but SQL 2000 Enterprise Edition only supports a maximum of 4
nodes so that is the limit. That is why I had to do an in-place OS upgrade
as a beginning step for this process. I normally don't like in-place
upgrades, but this was only for a short time during a transition.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:eP$dgeWNGHA.1192@.TK2MSFTNGP11.phx.gbl...
>I have a thought rolling around in my brain about limitations of the number
>of nodes being different between WIn2K and Win2K3...but I can't remember
>the specifics. Geoff, can you recall or am I off-base (anymore than
>usual?)
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.expertsrt.com - not your average tech Q&A site
>
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OF3pKh0MGHA.4052@.TK2MSFTNGP15.phx.gbl...
>
Thursday, March 22, 2012
can i develop on a different machine?
to create report projects from there, but I don't generally create
visual studio projects on the web server. I use a development machine
that does not have IIS installed. Is there any way to create report
projects on my development machine and point it to the report server?
I can't find any information on this, all of the examples I find tell
me to open a new report project, but the template only exists on the
report server. Is there some client tool I need to install?When you installed on the web server you installed both server and client
tools. Normally you would not have VS installed on the production machine
and only install the server part. Although it can be handy to be developing
on a machine that has both installed it is not necessary. When you preview a
report in VS it is not using IIS. Just install the client tools from the RS
installation on a machine that has Visual Studio on it.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"malpous" <porterdn@.email.uc.edu> wrote in message
news:97b85c30.0411221031.6907a8e2@.posting.google.com...
> I have just installed reporting services on our web server and am able
> to create report projects from there, but I don't generally create
> visual studio projects on the web server. I use a development machine
> that does not have IIS installed. Is there any way to create report
> projects on my development machine and point it to the report server?
> I can't find any information on this, all of the examples I find tell
> me to open a new report project, but the template only exists on the
> report server. Is there some client tool I need to install?
Can i create reports using VB Express and SQL Server Express?
Hi,
i ve installed visual basic express and sql server express. my question is can i create reports in my database application?
An update for SQL Server Express that includes a limited edition of Report Server is expected to become available in 2006. Its features are described here: http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx
-- Robert
Tuesday, March 20, 2012
Can i connect to SQLExpress instance using (local)
Hello,
I am using the following connection string to connect to SQL Server 2005 Express Edition installed on my local PC.
string sqlstr = "Server=(local);Database=MyDB;User ID=sa;Password=sa;Trusted_Connection=False";
And it gives me the following error. The string works fine in computer with SQL Server 2000 instance but fails with 2005. The string also fails for "Server = localhost".
However the string works very fine if I use the name of Server 2005 i.e ./SQLExpress
===================================
Cannot connect to (local).
===================================
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
Error Number: 2
Severity: 20
State: 0
Now the main problem is that, of course I could use a named instance, but since I am embedding the Connection String in a dll file so that any user can use it to connect it to the local instance of the SQL Server 2005 installed in his/her computer, I need to use "server = localhost". Doesn't SQL 2005 support this. If yes, where could i find option to enable it?
I have enabled every option available in surface area configuration for SQL Server 2005, but nothing seems to help out. I even use local as well as remote connections using both TCP/IP and named pipes.
Can nyone help me out?
Can I change the language settings after installation?
Hi All,
I have sql server 2005 dveloper edition installed on my XP pro. Both are English editions. I used the default language settings to install sql server 2005. The XP Pro has asian-language support installed and supports Chinese input.
I have tables with columns in nvarchar. But I can not input Chinese into the columns directly in the management studio or using sql statement.
How could I change the language so the Chinese chracaters being accepted?
Thanks a lot!
Gavin
You can change the collation sequence at the database, table, and column level. If you didn't specify any options, then the database will be created with your default collation sequence from the instance. If you change the collation sequence on the database or table to one compatible by the Chinese character set you are using, then you can input that data. You are going to need to drop and recreate the table since switching the collation sequence on the database doesn't automatically do so on the table.|||
Thanks Michael.
I remembered that it's not easy to do this in the previous versions (maybe I'm wrong?). So I think it is the same for 2005. When I was checking properties of the database, I noticed collation could be changed. I tried and it worked for me. I did not check the table and column level but I believe your are right. I may try them later.
Gavin
Sunday, March 11, 2012
Can i access SQL Login Users in ASP.Net application
I have SQL Server 2005 Installed and i have numbers of SQL Logins users which i want to use in my ASP.Net Application for authentication.
I am using ASP.Net 2.0 (VS.Net 2005).
Can i use the SQL Logins for ASP.Net web application authentication like the way we use Active Directory users?
Thanks in advance,
Wajahat Abbas
http://www.wajahatabbas.com
SQL Authentication is specific to SQL. You will not be able to use SQL Logins as you use Windows users.
See also:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconaspnetauthentication.asp
Thanks
Laurentiu
Thanks for replying.
Ya, i was thinking that with SQL 2005 and ASP.Net release, MS will increase the ASP.Net authenticaiton modes.
As SQL Server 2005 provides very cool features for SQL Users (like bad password, rating), so once we able to consume those things in ASP.Net it would be a peice of cake.
Anyway may be in next releases.
Thanks & Regards,
Wajahat Abbas
http://www.wajahatabbas.com
http://www.dotnetpakistan.com
Can i access SQL Login Users in ASP.Net application
I have SQL Server 2005 Installed and i have numbers of SQL Logins users which i want to use in my ASP.Net Application for authentication.
I am using ASP.Net 2.0 (VS.Net 2005).
Can i use the SQL Logins for ASP.Net web application authentication like the way we use Active Directory users?
Thanks in advance,
Wajahat Abbas
http://www.wajahatabbas.com
SQL Authentication is specific to SQL. You will not be able to use SQL Logins as you use Windows users.
See also:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconaspnetauthentication.asp
Thanks
Laurentiu
Thanks for replying.
Ya, i was thinking that with SQL 2005 and ASP.Net release, MS will increase the ASP.Net authenticaiton modes.
As SQL Server 2005 provides very cool features for SQL Users (like bad password, rating), so once we able to consume those things in ASP.Net it would be a peice of cake.
Anyway may be in next releases.
Thanks & Regards,
Wajahat Abbas
http://www.wajahatabbas.com
http://www.dotnetpakistan.com
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?
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 Create default instance with April CTP
It gets an error that the connection was refused. It works fine for a named instance.
Since all of the MSSQLServer registry entries are new, I don't think it is there. And all are done with the service Local Account. So I think the problem must be in the TCP/IP configuration referring to an old installation.
What is the problem? Is there a reference to all of these registry entries.
Thanks,
DavidIt's very difficult to provide you an answer given the information you provided. Are you trying to access the instance remotely or locally? By default, TCP is off. To turn on remote connectivity you can use either SQL Configuration Manager or SQL Server Surface Area Configuration Manager.
Dan
"This posting is provided "AS IS" with no warranties, and confers no rights"|||This occurs during the installation, so it is before the utilities are available. What communications method does the setup program use that can be refused. It is only refused for the default instance.|||Are you saying this works if you install a named instance? That's strange. Can you grab the log files from: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\*.log. You can zip the files before attaching them.
Thanks,
Dan|||Hi David
Probably setup is finding an default instance in the machine. I suggest that you uninstall previous build using the command line:
Start /wait D:\SQLDEV_CTP4\setup.exe /qb REMOVE=ALL
Start /wait msiexec /qb /X D:\SQLDEV_CTP4\Setup\sqlncli.msi
Start /wait D:\SQLDEV_CTP4\redist\2.0\dotnetfx.exe /q:a /c:"install /qu"
where D:\SQLDEV_CTP4 is the way for which you it extracted the of setup files.
Another option is to use Build Uninstall Wizard (\Setup Tools\Build Uninstall Wizard),but still I think that command line is more efficient to remove one previous build.
regards
Nilton Pinheiro
|||Sorry to say, I've got this exact same situation, and the above doesn't fix the problem.
Can Create default instance with April CTP
It gets an error that the connection was refused. It works fine for a named instance.
Since all of the MSSQLServer registry entries are new, I don't think it is there. And all are done with the service Local Account. So I think the problem must be in the TCP/IP configuration referring to an old installation.
What is the problem? Is there a reference to all of these registry entries.
Thanks,
DavidIt's very difficult to provide you an answer given the information you provided. Are you trying to access the instance remotely or locally? By default, TCP is off. To turn on remote connectivity you can use either SQL Configuration Manager or SQL Server Surface Area Configuration Manager.
Dan
"This posting is provided "AS IS" with no warranties, and confers no rights"|||This occurs during the installation, so it is before the utilities are available. What communications method does the setup program use that can be refused. It is only refused for the default instance.|||Are you saying this works if you install a named instance? That's strange. Can you grab the log files from: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\*.log. You can zip the files before attaching them.
Thanks,
Dan|||Hi David
Probably setup is finding an default instance in the machine. I suggest that you uninstall previous build using the command line:
Start /wait D:\SQLDEV_CTP4\setup.exe /qb REMOVE=ALL
Start /wait msiexec /qb /X D:\SQLDEV_CTP4\Setup\sqlncli.msi
Start /wait D:\SQLDEV_CTP4\redist\2.0\dotnetfx.exe /q:a /c:"install /qu"
where D:\SQLDEV_CTP4 is the way for which you it extracted the of setup files.
Another option is to use Build Uninstall Wizard (\Setup Tools\Build Uninstall Wizard),but still I think that command line is more efficient to remove one previous build.
regards
Nilton Pinheiro
|||Sorry to say, I've got this exact same situation, and the above doesn't fix the problem.
can connect using sql query analyzer but not osql or isql
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
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
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,
> >
> >
> >
>