I know that PerSeat is each individual computer that accesses SQL Server and PerServer is the number of concurrent connections to the server. Is Client Access Licenses the same as PerSeat?
At installation I erred in specifying per seat licensing when the server I'm working on is actually a per processor license. Can I change this or must I reinstall SQL 2K?
At installation I erred in specifying per seat licensing when the server I'm working on is actually a per processor license. Can I change this or must I reinstall SQL 2K?
This may seem like a stupid question but i have a server licensed per processor (4 processors) but would like to have it licensed per user. The licensing setup in control panel only shows options for per processor or per devide. How do i get to license per user without reinstalling?
I choose "PERSERVER" as licensing mode during the installation of the SQL Server by running the Setup. Now I want to change it to "PERSEAT" but I don't know how.
I have two question with respect to the developer edition licensing in SQL Server 2000 and 2005:
Question 1 I wanted to install a developer edition on a Development/Test Server. The server needs to be accessed by our development and Testing team of a team of 20 from their workstations. Is that possible?
Question 2 And if so what are the different licensing options that I can choose from considering that I don't want to install a developer edition of sql server on each workstation? The developer edition will be installed on the Dev/Test Server and the workstations will connect to the server using NT or Standard authentication.
I know i can use the sentence SET IMPLICIT_TRANSACTIONS ON in a Stored Procedure to force SQL Server to set the connection into implicit transaction mode.
Have i a sentence or configuration to force all SQL Server connections to implicit transaction mode?
one of my sql database went in suspect mode can any one advice why it has happened is it the problem with sql server . This has happend for the second time in 4 months .
SQL Users/DBAs,I'm trying to move data files around for a database that is in standbymode. I can detach/attach the database fine usingSP_DETACH_DB/SP_ATTACH_DB , but when I re-attach the database the logsequence is broken and I can't restore any more logs. Does anyoneknow if there is a way to move around data files and keep the databasein standby mode?Thanks,JB
We have SQL server 2000 on windows 2000. From our desktop MS Access was connected to database through ODBC. Since yesterday (after our consultant had updated another asp application in the same server) we are getting €œSQL Server Error: 18452. €¦.. Login failed for user €˜(null)€™. Reason: not associated with a trusted SQL Server connection. €œ
The consultant saying he did not touch any settings on server (?). And the problem is even server€™s security property shows it has mixed mode authentication. But I cannot connect to server even through my SQL server enterprise manager in windows authentication mode. I can connect if I use SQL server authentication. Through ODBC I can connect also and test fine, if I use SQL authentication. But the Access application wouldn€™t connect using SQL authentication in ODBC.
So, can any one help me to find out what else could be done to make sure that the server is going to accept windows authentication. I€™m thinking any other settings or registry change €¦ etc. Please help.
Finally figuring out that I can't use Express, I need to temporarily have my own SQL Server 2000 db server running. Hopefully just a couple of months, but who knows how long it'll take to convert over to MySQL.
Anyway, I need this db server to be on one machine. One web server will be accessing it (for one db).
What type of license do I need? Is it really the massively-priced per processor type? Or can I use another?
Currently we have SQL 7 standard server with 100 user CALs. We are planning to upgrade to SQL 2000. What happens to the CALs we have already purchased for SQL 7? Do we need to pay again for user CALs on SQL 2000? Or can we pay just for upgrade the server software?
We have a SQL Server 2000 Enterprise Edition box that contains roughly 100 Databases which does NOT have RS installed. Can we legally install RS on another (non-SQL) server without buying a SQL license, if it connects only to this SQL Server box?
If not, can we use a Standard Edition license for the RS box, and use it to connect to the EE box?
I didn't find any other forum to ask this and I didn't find any matching post for my question, so I post it here:
We have an application that is running on 2 web servers connected to a sql2000 server with a 2-processor license ... so I think there we have no problem no matter how many users are using our web application.
But the web application is producing a huge amount of logs that we want to analyze on a distinct multi-proc sql2000 server with a huge amount of harddisk space that's running with CAL licensing (not really sure how many we have for that server).
In a perfect solution we will provide access to the logs via our 2 web servers using the same application, but only for a given number of users (the number of users we hav CALs for). I think using that approach we get into licensing trouble.
Would it be ok to start a second web site on the same servers with an IP restriction allowing only "n" predefined IP endpoints so that only these machines can access the sql-Server that is running in CAL mode?
I'm not really sure what the CAL model really wants to allow - "n" physical users (persons), "n" end user computers, "n" database connections, max "n" of all together and is it concurrent, in a time of one day, the lifetime of the server? Maybe there's a document with some real world examples that I didn't find.
I have a client that has a licensed SQL 2005 environment running on a commercial site. I need to install SQL 2000 as well to support a piece of software that does not run on SQL 2005. The client believes that their license covers them to run both versions of the software - is this correct?
If so, they no longer have the install set for SQL 2000 so is there somewhere I can get this from? I work for a Microsoft partner so we have our MSDN version of SQL 2000 but I suspect that would not work with the clients key?
Unfortunately the client is in a different country so it's not easy to just try it and see.
I am in the process of migrating from Sql Server 2000 to 2005. Part of my plan is to move some database's to 2005, but use the 2000 compatibility mode for the short term. My issue is this, our DR boxes are still on SQL Server 2000, would I still be able to use our log shipping processes? Or would I be better off in starting with migrating the DR boxes to 2005 first?
We have reports in SharePoint integrated mode which are really slow when compared to native mode. I have been asked to research and give info on what exactly causes the delays.
Any articles which give me information as to what happens when a report is run from SharePoint server and where does it log.
Recently I read such statments 'When SQL Server is run in "lightweight pooling" mode (fiber mode) and the DTC service is started, unexpected behavior may occur.' Can someone say anything about fibe mode?I am appreciated for it.:)
I have a question about change of compability. I want to change compability level from 2000 to 2005 on a very large database with a lot of indexes. I have heard that if I change compability level the indexes will no longer be usable. Is it enough to just rebuild all indexed after I have changed compability level or do I have to do something else?
I have gotten my production version of SQL locked into single user mode. We recently upgraded to a clustered configeration and when I went to pause the system to get control I was told Pause was not available in a clustered environment. I restarted the service with -m [single user] but couldn't run Enterprise Manager as it appeared to take the only user slot and not give me one. Then I hit on startingup with Query Analyzer and that worked but now how do I get it back into multi-user mode. I placed the -m in the settings using Enterprise manager; could I stop the service and restart at the cmd prompt using -f [minimal config] and get Enterprise manager running? Any assistance appreciated.
I have a database that is in the SQL Server 2000 compatability mode on my SQL 2005 server. I am trying to restore a backup of this database on my SQL Server 2000 database on another server and keep getting strange messages. First trying Red-Gate and then plain SQL Server with no luck.
It seems as I remember that the 7.0 and 2000 compatibility issue between backups did not arise when the compatibility mode was set to 7.0.
Is this "planned" behavior or an "undocumented feature"??? Anyone else have success doing this?
I have a customer with an RS installation in a DMZ, using ADAM for its authentication.
The problem I have is as follows :
When setting up the execution log reporting (supplied as part of the standard install) all information being captured for report execution e.g Which user ran a specific report and when, is coming up with 'UNKNOWN' for the user name.
Does anyone have any idea where to look to fix the recording of user information? I am not sure whether it is a RS or A.D.A.M issue.
I€™m having a problem setting up maintenance plans on one of our SQL 2005 servers but first here€™s a bit of back ground.
The server is a Virtual machine running win2k3R2 SP2 server std and SQL 2k5, A supplier arrived to install and app on the server when discovering there app didn€™t work with 2k5 they seem to have set the 2 dbs on the server into 2k compatibility mode and set the entire SQL install to think its a 2000 install. (I€™m not sure how this is done all I can see is the wrong version number in management studio) The problem this is giving me it that the folder in management studio for Database Maintenance Plans is no longer under the management folder instead it under a sub folder called Legacy (which is how management studio seems to deal with all registered 2000 instances) and as such a can no longer right click and create new database maintenance plans is there any way around this or will I have to setup my backup job manually?
If SQL Server 2000 is loaded onto a 8 processor machine, can I legitimately load Standard Edition, which will only use 4 of the 8 processors, or as some interpretations of the license suggest, must I purchase Enterprise Edition (i.e. you are not permitted to load SQL Server on a machine which has more processors than the Product is capable of using) ?.
I know the "reasonable" answer, but what is the legal position ?
My company is embarking on a data warehousing project. We are going to purchase a Windows 2003 server. It would be a dual processor. The specs are not certain yet so cannot give more details on that.
1. The data in the warehouse would be close to 150 GB. 2. There will be maximum of 10 users needs a SQL Server license. 3. Do not need analysis services.
What edition do I go with -Enterprise OR Standara? I want the least priced edition. I looked up the various links on Books Online but I am still not able to decide.
Say I need only 2 GB of RAM. Then here are my questions.
1. Since we are going with a dual-processor, do I need to purchase processor license for each of the two? Why can't I have one license on one processor only? What are the implications of this?
2. The 10 users that I am talking about will be remotely connecting to this Windows 2003 server and accessing the databae.
3. What exactly is Failover clustering? Do I really need it for my warehousing project?
4. Please help me pick the correct license. Here is the link -
Is there a way to find the SQL Server licensing information after the software is installed? I mean is there a way to say that it was licensed per cpu or per cal?
I have a Windows 2000 Operating System with 4 processor, out of which I'm planning to use only one Processor for the SQL Server and leave the rest of the three processor for the OS. My question is that do I need to buy the license for all the 4 processors or I can do with the only 1 that will be used for running the SQL?