Tag Info

Hot answers tagged

17

SQL Server instances have separate sets of binaries for each installation. For the base engine, you will have separate SQL Server and SQL agent services that can run under separate accounts. They each have their own configurations and users. This is also true for other components like Analysis Services and Reporting Services if you install them. There ...


16

If I have 8GB of RAM in a server and I run 4 instances of SQL Express, will the total memory limit used by SQL Server be 1GB or 4GB? Each instance can use up to 1GB of memory for the buffer pool. Each instance can use a bit more than 1GB in total because not all memory allocations go via the buffer pool. In your case, the maximum memory used by the ...


13

It's not possible. You need to reinstall it. There is no instance rename facility for the Database Engine. http://social.msdn.microsoft.com/Forums/en/sqlsetupandupgrade/thread/d5d297b0-2995-46ba-9d3b-d1ec8825f479


10

We are mounting a database to an instance. See the concepts guide: The instance mounts a database to associate the database with that instance. One way I've seen it explained (probably here or on SO) is that the instance is the memory structures and processes, and the database is the data on disk. The instance has to have a database associated with ...


9

No, no and again no. One instance, one server, Always. The reasons have to do with the SQL Server memory manager and CPU scheduler architecture, it really works best if it has the whole box to itself and nothing else runs on the box. 'Partitioning' of resources (max server memory, affinity mask) solves some problems and introduces more. If you want to ...


9

Integration Services is not "Instance aware". The rest (Analysis, Reporting, DB) are. Note that SSIS doesn't need to be instance aware either. The service itself is pretty pointless and doesn't need to running. You simply need the SQL Server common binaries installed to run packages. The service is for SQL Server Agent and SSMS to browse packages etc ...


8

Are you running from the 10gen repository or from the default Debian/Ubuntu repo? I recommend using the official 10gen repository. Check this link out - [10gen MongoDB How-To Install on Ubuntu:] http://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/. It is best to uninstall the previous mongodb installation prior to this change, which will also ...


5

The SQL Server Customer Advisory Team wrote a blog post that has some information on this setting here. The –E startup flag The SQL Server startup flag –E forces SQL Server to allocate 4 extents at a time to each file, essentially quadrupling the stripe size. In heavy insert scenarios, this drives larger block sizes to the disk. Also, your pages ...


5

Think of it this way: the database is the set of physical files, on disk. It's a completely passive "thing". It doesn't "do" anything on its own - it's just data. the instance is the software/processes (with its memory) that manages the database. It's the active part. It's what clients connect to, it's what processes SQL, reads data, updates it, maintains ...


5

Instance Recovery is necessary to get the database back to a consistent state after shutdown abort or some other abnormal shutdown event. Oracle is never going to let you open the database in an inconsistent state, so no, there is no possibility that you can disable it. If Oracle is crashing during Instance Recovery you need to get in touch with Oracle ...


5

I can see why this might be confusing given the mental model we apply to the word mount. It may help to think of mount as an abstract Oracle term and only apply to it what the software actually does. Here are the stages of instance and database startup: Shutdown NoMount Reads the parameters in the initialization file. Allocates memory. Starts the ...


4

You cannot change the instance name, but if I may suggest, you may be able to use server aliases instead. Eg: if your DB server was stackexchange and the instance name was sql2005, you would connect to the sql server by going to stackexchange\sql2005. An alias can be setup in the SQL configuration manger with a name of lets say dbaxchange and then pointed to ...


4

Almost nothing is going to be shared. From the perspective of the actual SQL Server services nothing is shared. Each instance get's it's own services and each has their own copies of the actual EXE files. Only one copy of the management tools is installed, and things like drivers are shared.


3

When you added the new server name using sp_addserver, did you remember to include the "local" designation. It is that tag that updates the metadata for @@SERVERNAME. More information. sp_addserver 'servername', local


3

Based on your sample data, the data you're actually querying for ID = 1396779 is different No amount of trims, isnulls etc will change Schmoe into Frost or Jack into Joe. Ergo, data is different. Otherwise, you have some DB or Server confusion going on. A report based on the DataWarehouse can't give correct data if your query against the DataWarehouse is ...


3

Not sure I fully understand all of the variables but I suspect you would be able to use synonyms that are different between the two environments which would allow the code to be the same. It is a layer of abstraction that requires documentation and/or an extra layer of the onion to peel, but can definitely simplify the code you write. Here is the CREATE ...


3

Umm, not sure if this helps, but we're using a set of scripts to "clean" a production database and prepare it for development abuse. We're taking all the big tables that have a datetime column and we're rebuilding the table with only the last year of data in it. From a full db of about 200 GB we get to about a 40 GB db for development. Mainly we're ...


3

You can delete databases with DBCA which takes care of most of it. Or you can do as below, but this will do the same as removing the datafiles, redo logs, controlfiles manually. sqlplus / as sysdba startup mount exclusive restrict exit rman target / drop database including backups noprompt; exit After this, you still have to remove the entry that belongs ...


3

If the DB is running, you can look for the pmon process: ps auxww | grep pmon | grep -v grep You'll see one pmon process for each database that is up. For example ora_pmon_YOURDB, where YOURDB is the instance name. You can also ask the listener which services it is serving connections for, with: lsnrctl status


2

I don't think it is possible to upgrade SQL Server Express to another edition. You should be able to use all the features of SQL Server you mentioned (agent and profiler) with the new, named instance (DEVEDITION) along side of Express Edition. I don't think its possible to rename a SQL Server instance name, at least not with a bunch of headache. What I ...


2

No, you do not have a name collision. Your DB_DOMAIN, DB_NAME, and INSTANCE_NAME can all be identical as long as the databases are on different hosts (as you have indicated). However, as others have stated using the same DB_NAME is a bad idea for anything other than perhaps a recovery operation. A policy enforcing distinct passwords will be broken. ...


2

In general, it would mean that the instance that was servicing the request failed and is no longer running. In a RAC cluster, you run one instance on each node of the cluster. I wouldn't make sense to move an instance from one node to another in the cluster-- that would imply that one node would be running two instances of the same database. Depending on ...


2

Create a Server Alias to point to your named instance. In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, right-click Aliases, and then click New Alias. In the Alias Name box, type the name of the alias. Client applications use this name when they connect. In the Server box, type the name or IP address of a ...


2

There's only a couple of "gains" that I can think of off the top of my head. First off, security. If for some reason a login had to have elevated permissions on the instance but there are sensitive databases then that could potentially be a reason to have multiple instances on the same box. Another one would be the requirement for different SQL Server ...


2

It might be helpful to review DB2 in general first. When you install DB2 it creates an instance. Think of this as a "server". An instance can have zero to many databases within it (can't say I know the limit). When you created DB2 locally it created an instance for you named DB2. Usually when you install DB2 on say a Unix server, you name your instances. ...


2

@Chris Aldrich has given a good explanation. I will just add a few things here. 1) There is no concept of a "database user" in DB2. All authentication happens outside the database or instance, in the operating system. Also, there is no direct relationship between a user ID and a schema name, unlike in Oracle. In DB2 a schema is just a logical grouping of ...


2

Another option is to add additional IP addresses to the machine (does not require an additional network card to the best of my knowledge) each one with a different DNS entry. So now you can connect to that machine using multiple names. Then you set up the IP address in the TCPIP settings for the instance (using configuration manager). Each of those IP ...


1

No, unfortunately there is no magic "be like that guy" feature. What you have to do is either: install RTM and then apply the SP + CU; or slipstream the same SP + CU into the RTM binaries and install that. These instructions are applicable to both SQL Server 2008 and SQL Server 2008 R2, though the process is a little easier in SQL Server 2012. The former ...


1

The same SERVICE_NAME can run in multiple instances with a RAC, and in a physical standby database, those services also exist. In fact, you'd need them to be running in order for failover to work. Service name from a uniqueness perspective only matters in terms of being unique within a particular listener's purview; it's how the listener routes ...



Only top voted, non community-wiki answers of a minimum length are eligible