Hot answers tagged instance
15
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
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 ...
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
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
...
7
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 ...
7
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-debian-or-ubuntu-linux/. It is best to uninstall the previous mongodb installation prior to this change, ...
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
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 ...
3
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 ...
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 ...
1
The documentation explains it very well:
An Oracle database server consists of an Oracle database and an Oracle
instance. Every time a database is started, a system global area (SGA)
is allocated and Oracle background processes are started. The
combination of the background processes and memory buffers is called
an Oracle instance.
An oracle ...
1
I use the following to identify problems and build the correct drop and add statements, if you get ALL OK, then you don't need to do anything otherwise you need to run the commands.
declare @currentName as nvarchar(128)
declare @newName as varchar(max)
declare @serverName as varchar(max)
declare @serverInstance as varchar(max)
select @currentName = ...
1
I ran into a problem with the above answer where stop-start-daemon doesn't start a new process with the same name more than once. However, there is a --name argument that allows you to change the line in your upstart script in /etc/init/ to include a new name so it'll start. Something like this:
if [ "x$ENABLE_MONGODB" = "xyes" ]; then exec ...
1
The primary difference is in your TNSNAMES.ORA file deployed for your clients. The connection names there will differentiate which server+instance combination you intend on working with.
The DB_NAME / INSTANCE_NAME has a couple of purposes, both for failover databases, or RAC (cluster) databases. These would share a db_name, but have unique instance_names.
1
I found the answer yesterday with the help of a friend of mine. I had to log in via SSMS with a user other than the Windows login I was attempting to use, delete the old login, and add my Windows login again. After that, I was able to transfer ownership of the job properly, SQL was able to get the user data from Windows, and all was right with the world.
Only top voted, non community-wiki answers of a minimum length are eligible
