Not posted here for a while as been stupidly busy, but here goes:
This might sound a bit of a silly question, but what issues will I come across with installing a new instance of SQL on top of a single instance setup?
The server I have to do this on is currently live on the existing instance and I can't afford any downtime (apart from a 10 minute reboot if rellay required).
I'm trying (and have been for ages) to install a MSDE server with a different instance name than the default. Im setting the instancename when using the setup.exe file and all seems to install fine, but when I then restart my system the SQL icon appears in the system tray but the white circle is completely empty. It says that it is not connected.
If i install with the default instance name then all seems to work fine.
Does anyone know what I am doing wrong and what I can do to fix this problem?
When I try and install a new instance alongside the default instance setup appears to hang when asking for the type of installation, ie. Typical,Custom,Advanced. I had to kill the setup process, however the original instance still works. Has anybody had any similar problems during setup. Thanks in anticipation.
I have installed sql2005 default instance, and I need to install anther named instance. but when I tried to install the s/w it does not give option for new instance instead, it shows only uninstall option.
I want to install SP2 for SQL 2012, but I am not sure how my instance would be affected.
I want to know if the instance will go down for any amount of time during the update? I can schedule a server reboot after hours, but don't want to apply the service pack if it will take the instance offline at any point.
I have a problem installing a SQL Server 2005 (developper edition) on my windows XP SP2 machine.
When I launch the setup, all the requirements are ok, but I'm just allowed to install client components and documentations. I can't install the database server instance.
The Sql Server is downloaded from MSDN (2 iso files extracted to my HD)
My machine is a P4 2.8Ghz HT with 1Gig of RAM.
Thanks for your help
FYI, here's the Report for the system configuration check:
I will be installing a second SQL 2005 instance on an existing SQL 2005 clustered installation. We've added a set of disks for the new instance. My question is, will the existing clustered instance need to be taken offline for the installation, or will the nodes need to be rebooted after installing the new instance?
I haven't been able to confirm this on MS website or by Googling.
I understand we need to ensure no one is logged in to the remote nodes during the install as well.
Hello all (sorry for the cross post, I previously posted that message in getting started)
I have a problem installing a SQL Server 2005 (developper edition) on my windows XP SP2 machine.
When I launch the setup, all the requirements are ok, but I'm just allowed to install client components and documentations. I can't install the database server instance.
The Sql Server is downloaded from MSDN (2 iso files extracted to my HD)
My machine is a P4 2.8Ghz HT with 1Gig of RAM.
Thanks for your help
FYI, here's the Report for the system configuration check:
I clicked on the setup.exe file which is located in C:sql2ksp3MSDE directory , then the following Error message appear to me:
========================================= ---------------------------------------- Microsoft SQL Sever Desktop Engine ---------------------------------------- The instance name spacified is invalid.
=========================================
What is the solution??
FYI: I am using: MS Visual Studio.NET 2003 MS Windows XP SP1a MS SQL Server 2000
I just upgraded ACT database and it needs SQL Server. I just keep getting "SQL Server Setup Failed". I downloaded SQL from Microsoft, went to install and get the same error. It then refers to a summary txt log which I have had a look at but to be quite honest means nothing to me.
Given than once SQL Server 2005 is installed, SQL Server Studio has to be used instead of Enterprise manager, can both SQL 2000 and 2005 be used on the same machine, be it development or production? (The second one to be installed probably would be a named instance.) Any experiance of doing this or a pointer to a Microsoft recommendation would be appreciated.
We've devoted a resource to this today, but I have to believe it's something easy that we're overlooking. The scneario is that we have a production Web application that until last weekend had a SQL 2000 back end. This weekend we installed a new instance of SQL 2005 and everything works (we tested in a sandbox environment, but someone must not have load tested enough) and never saw these exceptions. So, after the upgrade we now receive 100's of thexe SQL excptions per day:A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)Does anyone know what we've overlooked that's causing this issue?Thanks for any help!
would like to know if it's possible to install SQL Server Failover cluster instance with shared storage along with standalone installation with Always on ( always on uses WSFC underneath).
I've two instances(Default, Named[dynamicsFINANCE]) running on SQL server 2014. However, when I try to connect to named instance say (dynamicsFINANCE) using SQL authentication from local SSMS, I get below error message:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
I assigned a static port number to the named instance [dynamicsFINANCE] 1450. I also setup the firewall rule to allow access to Port 1450.
I have to migrate all objects alogwith all constraints,SP,Triggers, indexes etc from Development instance to Production instance of a DB, all those things are created through wizard ie. Sql server 2000 Enterprise Manager. if i use DTS it only mirates data along with tables and views but constraints,SP,Triggers, indexes etc not yet copied.
can any body help me how can I solve this problem by copying all objects alogwith all constraints,SP,Triggers etc from Development instance to Production instance.
I have a 3 node cluster on which I have installed SSAS as it's own insntance. I have created this as a named instance and can connect to it by serverinstance if I'm on the server itself. However from my desktop I get the error saying instance was not found on server name.
I have defined an alternate port and setup firewall rules and can connect via server:port but not serverinstance. Prior to making this change SSAS was running on default port of 2383 and I could connect just by servername.
I have read many articles for previous versions saying that clustered SSAS will always use 2383 and that you must connect just using servername. However and this is were it gets strange. I have a 2 node UAT cluster with SSAS setup exactly the same way I've described above and I can connect from my desktop as serverinstance.
Should I be able to connect as serverinstances for a named clustered instance in 2012 ?
Is it possible to install and configure the MSDTC resource in a SQL Server 2000 cluster after SQL is installed and running?
When I recently went through a rebuild of my cluster, I forgot to install the resource before installing SQL Server. Now, if I install and bring online the MSDTC resource the SQL disk groups will not fail over correctly. The SQL Server resource will not come online.
Thanks in advance for any help. I would really like to avoid rebuilding again.
Hi, I have a task in hand to migrate (upgrade) from SQL2K named instance to SQL2K5 default instance. There are many intranet applications touching current SQL2K. I would like to perform this upgrade such that I don't have to touch any application code - meaning I don't have to change the connectionstring to point to new Default instance. How can I achieve this?
So, in otherwords, here is what I want to achieve:
Current Server: SQL2K: SERVER_AINSTANCE_A (named instance)
If I have both default, I could achive this by setting up DNS alias after migration done so that any call for SERVER_A would point to SERVER_B. But in my case, I don't have SERVER_A, I have named instance. Is there any solution?
I want to move one database from the source SQL Server 2000 instance to a new SQL 2000 instance in another machine. I have five user databases in this source SQL instance. How should be my approach to move this single database out of this ? My understanding is restoring this database in the new instance, copying all logins to the new instance and then copying the jobs, DTS packages, alerts, operators only specific to this database will do it. Please let me know if this is exactly what I should do ..
I want to move one database from the source SQL Server 2000 instance to a new SQL 2000 instance in another machine. I have five user databases in this source SQL instance. How should be my approach to move this single database out of this ? My understanding is restoring this database in the new instance, copying all logins to the new instance and then copying the jobs, DTS packages, alerts, operators only specific to this database will do it. Please let me know if this is exactly what I should do ..
I am trying to set up a Named Instance of SQL 2000 on the same machine that has a default instance of SQL 7.0. The setup always completes and I am able to register the Named Instance of the SQL Server with which it was installed on. However, when I try to connect the users to the database, with both windows and SQL authentication, I receive a SQL server not found error. I have tried an alias setup as well as physically specifying the port number in settup up an ODBC connection. Has anyone ran into similar problems? Also, has anyone been able to successfully complete the process as mentioned above?
I have a server with sql server 2005 installed as the default instance -- I have a piece of software that needs SQL2000 to be the default instance. Is there a way other than install new sql2005 named instance and move databases to rename my SQL2005 instance from <machinename> to <machinename>sql05 for example?
i have installed SQL client instance on my Desktop "Machine-A", and i used to connect to SQLServer2000 running on another "Machine-B" by using valid username and password.
i created a DTS package and i used to run it. im very confused how the communication happens between the two machines and which process run where and which initiates which and which machine allocates waht resources. im really interested to know all these things. if any one know plz help me out.
I work for a mid size company with the usual collection of enterprise applications. We are trying to consolidate our SQL environment consisting of around 100 databases none of which are over 100GB with the average database size around 5GB. Recently a large server was purchased as the "Big Daddy" SQL box. Obviously not all the databases will be moved to this one box but within reason a number can.
My question: What is the best way to configure the box?
1 OS & 1 Default Instance - How do we isolate loops memory leaks etc... 1 OS & Multiple instances, ie:Dedicated instance for each application. - How do you allocate CPU & memory, allow for optimum performance without putting others at risk from a rouge process? Virtualized OS for each application with a default instance - Too much overhead impacts performance?
Future plans include offsite replication, perhaps mirroring with failover.
I'd appreciate anyone else's thoughts ideas? How have you tackled this problem in your environment?
I installed SQL Server 2005 recently on a cluster. I didn't go for the default instance and instead I named the instance option. Now I would like to migrate everything from the named instance to the default instance, which I haven't yet installed.
Is this an easy process? What about the logins and the maintenance plans and jobs? Is there anything else I need to be aware of?
I've never had to do this, but when I downloaded the Web Workflow Approvals Starter Kit, it requested that I install the database into a User Instance of .SQLEXPRESS.
Now the problem is, I've installed it onto a default instance, so I was wondering whether you can create a named instance on top of a default instance... and if so, how would you do that?
Got windows Vista Business edition, installed Visual Web Developer Express, SQL Server 2005 Express SP2, SQL Server Management Studio SP1 in that order. I was developing in VWD express without problems using WinXP but now on Vista Business, the local connection to SQL server appears to be a problem. I know there's nothing wrong with my web.config or anything like that as it was working perfectly prior to running under Vista. If i specify the database on the live website, it works fine. If I specify the test database in app_data folder, I get the following exception:-
Server Error in '/UKSD' Application.
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[SqlException (0x80131904): Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +736211 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1959 System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +33 System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +237 System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +374 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +192 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197 System.Web.Security.SqlRoleProvider.GetRolesForUser(String username) +771 System.Web.Security.RolePrincipal.IsInRole(String role) +272 System.Web.Configuration.AuthorizationRule.IsTheUserInAnyRole(StringCollection roles, IPrincipal principal) +120 System.Web.Configuration.AuthorizationRule.IsUserAllowed(IPrincipal user, String verb) +300 System.Web.Configuration.AuthorizationRuleCollection.IsUserAllowed(IPrincipal user, String verb) +191 System.Web.Security.UrlAuthorizationModule.OnEnter(Object source, EventArgs eventArgs) +3509206 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
Version Information: Microsoft .NET Framework Version:2.0.50727.312; ASP.NET Version:2.0.50727.312
I am taking a guess it's somerthing to do with access issues, but can't find anything out on searching the forums etc.. I am setup as an administrator, running VWD as an administrator and for the record, SQL Server Management Studio express works fine. Another small issue, when I run the application from VWD, I always have to minimise the application and restore it as the graphics get corrupt. Please help!! I cannot debug when running of the live website.
The box I am trying to connect to is running two instances of SQL Server. There is a SQL Server 2005 instance which is the default. There is a SQL Server 2000 instance which is named 'SQLSERVER'. I can connect to the SQL Server 2000 instance no problem:<add key="ConnectionString" value="server=MYPCSQLSERVER;database=mydatabase;user id=****;password=****" /> However, I am having trouble connecting to the Default SQL Server 2005 instance. I have tried: <add key="ConnectionString" value="server=MYPC;database=mydatabase;user id=****;password=****" /> but it doesn't work. I have tried explicitly setting SQL Server 2005 to use port 1434 (as SQL Server 2000 is running on port 1433), and then used: <add key="ConnectionString" value="server=MYPC,1434;database=mydatabase;user id=****;password=****" /> but this doesn't work either.
Am I mssing something here? Any help much appreciated Thanks...
As a starter i tried to modify and translate the Personal Website Starters kit from the VS2005Team SDK.
When i'm working on the machine were it's installed , under debugging, all works great.
But when i try to develop from my laptop, via RDP on the develop machine, i've got this message and can not debug (connect to the SQLxpres Server)
Does anybody now a solution ?? Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
Source Error:
Line 5: Sub Application_Start(ByVal sender As [Object], ByVal e As EventArgs) Line 6: AddHandler SiteMap.SiteMapResolve, AddressOf Me.AppendQueryString Line 7: If (Roles.RoleExists("Administrators") = False) Then Line 8: Roles.CreateRole("Administrators") Line 9: End If