Sql server 2005 backward compatibility
Dear all,
I have a stored procedure which use the below code and was developed in Sql server 2012.
;WITH CTE
AS
SELECT *,
ROW_NUMBER() OVER(PARTITION BY SUPPID ORDER BY JDATE ASC) AS RCount
FROM #VDN
My question is whether the same procedure will be compatible with Sql server 2005. Please clarify.
Thanks in Advance.
We have both
ROW_NUMBER (Transact-SQL) and
WITH common_table_expression (Transact-SQL) since SQL Server Version 2005, so yes, it will work.
Olaf Helper
[ Blog] [ Xing] [ MVP]
Similar Messages
-
Instalation of SQL server 2005 Backward compatibility components in Windows Seven
Anyone can help me to install de SQL Server 2005 Backward Compatibility componentes in Windows 7 home, Intel Core Duo
It say that is not compatible.
Thanks in advance.Hi,
We can see this feature pack was issued in Nov 2005 from the site, which may not be updated
to add Windows Vista/7 to supported operating systems. However, I can download and install X64 (64-bit)
Microsoft SQL Server 2005 Backward Compatibility Components on Windows 7 Enterprise 64-bit successfully.
If you get any error while installing, please let me know.
Thanks,
Chunsong
Please remember to mark the replies as answers if they help and unmark them if they provide no help. -
Looking for SQL 2005 Backwards Compatibility ((( 8.05.2309 )))
We need to find the install for SQL 2005 Backwards Compatibility 8.05.2309 64 bit.
Can someone help with locating the install for this?
Thanks in advance for your assistance
EdEd, would SQL Server 2005 Backward Compatibility Components version 8.05.2312 work for you?
http://www.exactsoftware.com/docs/DocView.aspx?DocumentID=%7B21509a73-9043-47d8-854c-318a3a35b585%7D -
SQL Server 2005 Dev Integration Services Fail
I've got VS2005 v.8.0.50727.867 (vsvista.050727-8600) on my 64bit Windows 7 box. I am trying to install SQL Server 2005 Integration Services on this Win7 box so I can load and edit the Win XP SSIS projects that I had on my XP box. So far I've
not been able to successfully install the Integration Services with a failed permission on the SQL**DTD.msi file.....I've copied this file locally and tried to run it and it would start but then would give permission error.
Is there an inherent incompatibility running SSIS projects in SQL Server 2005 on a 64bit Win 7 box? Worked great on my XP box.
I've been "upgrading" the SSIS projects to VS2008 since I was able to get SSIS installed. Any ideas what I need to do to get this beast to work?
TIA
HarryThanks Alberto
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Professional Service Pack 1 (Build 7601)
Time : Mon Aug 25 09:31:30 2014
DT0315 : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features,
install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL
Server in Books Online.
DT0315 : Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_1.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_1.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_2.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_1.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_2.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_2.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_3.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_2.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_3.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_3.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_4.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_3.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_4.log
Machine : DT0315
Product : Microsoft VSS Writer for SQL Server 2012
Product Version : 11.0.2100.60
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SqlWriter_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_4.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_5.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_4.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_5.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BOL_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_5.log
Machine : DT0315
Product : Integration Services
Error : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Machine : DT0315
Product : Microsoft SQL Server 2005 Integration Services (64-bit)
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_DTS.log
Last Action : InstallFinalize
Error String : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Error Number : 29549
Machine : DT0315
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQL.log
Machine : DT0315
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_2.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Analysis Services (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_AS.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Notification Services (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_NS.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Tools (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_Tools.log
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt. -
SQL Server 2005 Workgroup Edition compatibility for SAP B1 2005B
Hi Experts,
Please advise SQL Server 2005 Workgroup Edition can be used as the backend for SAP Business One 2005B.
Thanks,
ShakeelHi
Please go to:SAP service portal-product availability-supported platform-database platform
For 2005 B version we could get the following supportted information:
Microsoft?SQL Server 2005 SP2
- 32 Bit / 64 Bit (x64)
- Express (3), Workgroup (4), Standard & Enterprise Edition
Please read SAP Note 928839 on how to order SQL 2005 for upgrade purposes.
(3)SQL 2005 Express Edition is only supported with the SAP Business One Evaluation Versions and only in 32 Bit mode.
(4)SQL 2005 Workgroup Edition is only supported with Windows Small Business Server (SBS) 2003 and only in 32 Bit mode
For more detailed information regarding the supportted platform you could refer to the webpage from the above path.
Best Regards
Helen Sun
SAP Business One Forums Team -
Compatibility of Toplink with SQL SERVER 2005 Enterprise edition
Hi All,
We have J2EE application developed using TopLink ORM, which is running on SQL server 2000 standard edition, and now we are planing to migrate the SQL server 2000 to SQL server 2005 Enterprise edition, so please let me know whether TopLink supports for SQL server 2005 Enterprise edition or is there any disadvantages.
Looking for your advice earliest
Thanks in advance.
Anand Siddacharya.Yes, TopLink supports any SQL compliant database with a JDBC compliant driver.
As long as you have a JDBC driver that works correctly, I can't see any issues in the upgrade.
James : http://www.eclipselink.org -
SQL server 2005 SP3 can run SAP B1 2005A SP01 PL51
Hi All,
I could successfully install SAP B1 2005A SP01 PL51 in the SQL server 2005 SP3.
In this link:
http://service.sap.com/smb/sbo/platforms
you won't find it such info.
Why I upgrade, it is caused by the printing error issue using citrix.
Anyone of you that have problem after run the B1 on that SQL, pls share.
Someone who need webex file that shows the install process can request it to me. Let me know.
Rgds,Hi Arshdeep,
Thx for your reply. I just wonder why SAP did not inform the availability SP3 from Microsoft and the explanation about the inapplicable of SP3 for SAP B1 in the B1 platform link.
I have tested without using any steps and any other procedures. Practice is a good lesson to learn for me. Nevertheless, one concern from modern customers are the compatibility or adaptibility of SAP B1 to Microsoft product especially SQL since it is one of database platform.
Old-fashioned customer will disregard that because they will think as long as my SAP B1 and SQL server still run well, I don't care..
Rgds, -
MS-SQL Server 2005 SP1 vs MS-SQL Native Client 2008 or 2012
Hello,
I woud like to know if it's possible to use on a computer Windows Seven, the MS-SQL Native Client 2008 or 2012, and connect it on a MS-SQL Server 2005 (under Windows 2003 enterprise).
Regards,Hello,
Yes, the SQL Server Native client is backward compatible, means you can use Client 2008 or higher to connect to a SQL Server 2005.
With some limitations the client is also forward compatible, means you can use a client 2005 to connect to SQL Server 2008 and higher; but the client isn't aware of new server features.
Olaf Helper
[ Blog] [ Xing] [ MVP] -
MS SQL Server 2005 - Express Edition?
I am interested to learn about database development for use
with CF dynamic development. Before I make any significant
financial investments I'm wondering if
MS SQL Server 2005
Express Edition is a reasonable place to start learning
about db development.
The Adobe ColdFusion 8 SYSTEMS SUPPORT MATRI X indicates
compatibility with: MS SQL Server 7.0, 2000, 2005 - Does this
compatibility include the FREE
MS SQL Server 2005
Express Edition ?
Does it bother MS that folks may want to use their db
solutions with a competitor's dynamic-development solutions? In
other words, are the compatible db products fully functional with
CF?personally i like ms sql as i have always used it and am
familiar with it. I think mysql is the choice more for PHP
developers and I think CF works better with MS SQL. A definate
choice of preference though, i ilke the way i can install as many
instances as I like.
eg 1 for websites
1 for applications etc
there is merit in both but here in UK/Ireland mysql is not as
popular as MS SQL. -
Troble configuring Hyperion Shared Services with SQL Server 2005
I recently installed SQL server (SQL SERVER 2005) in my machine and then am trying to install Hyperion (9.3.1) products. I started with Shared services. It was installed successfully. Problem is occuring when am trying to configure Shared service with SQL database using Hyperion Configuration utility (9.3.1)
The error which is popping up is
Unable to connect to the database for the product Hyperion Shared Services.
Things which I tried from my end
1. Made sure TCP IP Protocol was enabled in SQL server configuration server.
2. hypuser was created in SQl server.
3. hypdb was created in SQL server.
4. Was having dynamic IP address so install Loopback adapter to obtain Static IP address and port.
5. Port and IP address was correct.
Let me know where I am going wrong.
Any help will be greatly appreciated.Finally got it fixed firewall settings needed to be change : This document helped me a lot to troubleshoot the issue
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) (Microsoft SQL Server, Error: 2)
This problem may occur when SQL Server 2005 is not configured to accept incoming local and remote connections, which is disabled by default in SQL Server 2005 Express Edition, SQL Server 2005 Developer Edition and also SQL Server 2005 Enterprise Edition. To solve the connection forbidden problem, SQL Server 2005 needs to configure to allow incoming local and remote connections.
Firstly, ensure that SQL Server 2005 is configured properly to allow incoming connections on the instance of database server, else enable and turn on the local and remote connections setting.
Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Surface Area Configuration.
On the “SQL Server 2005 Surface Area Configuration” page, click Surface Area Configuration for Services and Connections.
On the “Surface Area Configuration for Services and Connections” page, expand Database Engine tree, click Remote Connections.
Select Local and remote connections, or Local connections only which applicable only if there is no remote system tries to connect to the SQL Server, useful when you just trying to connect and authenticate with the server after installing.
Select the appropriate protocol to enable to local and/or remote connections environment. To ensure maximum compatibility, select Using both TCP/IP and named pipes.
Click Apply button when done.
Click OK button when prompted with the message saying that “Changes to Connection Settings will not take effect until you restart the Database Engine service.”
On the “Surface Area Configuration for Services and Connections” page, expand Database Engine, then click Service.
Click Stop button to stop the SQL Server service.
Wait until the MSSQLSERVER service stops, and then click Start button to restart the MSSQLSERVER service.
Secondly, SQL Server Browser service has to be enabled to allow for local and remote connections if SQL Server 2005 is running by using an instance name and users are not using a specific TCP/IP port number in the connection string.
Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Surface Area Configuration.
On the “SQL Server 2005 Surface Area Configuration” page, click Surface Area Configuration for Services and Connections.
On the “Surface Area Configuration for Services and Connections” page, click SQL Server Browser.
Select Automatic as the Startup type to start SQL Server Browser service automatically every time system starts.
Click Apply button.
Click on Start button to start the service immediately.
Click OK button.
Finally, if remote computer needs to connect and access SQL Server, an exceptions in Windows Firewall included in Windows XP SP2 (Service Pack 2), Windows Server 2003 and Windows Vista needs to be created. If you’re using third-party firewall system, the exception rules also needed to be created to allow external remote connections to the SQL Server 2005 and SQL Server Browser Service to communicate through the firewall, else connections will be blocked. Consult the firewall manual for more details. Each instance of SQL Server 2005 must have its own exception, together with an exclusion for SQL Server Browser service.
SQL Server 2005 uses an instance ID as part of the path when you install its program files. To create an exception for each instance of SQL Server, you must identify the correct instance ID. To obtain an instance ID, follow these steps:
Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Configuration Manager.
In “SQL Server Configuration Manager”, click the SQL Server Browser service in the right pane, right-click the instance name in the main window, and then click Properties.
On the “SQL Server Browser Properties” page, click the Advanced tab, locate the instance ID in the property list.
Click OK button.
Then create an exception for SQL Server 2005 in Windows Firewall.
Click on Start button, the click on Run and type firewall.cpl, and then click OK. For Windows Vista, type firewall.cpl in Start Search box and press Enter key, then click on Allow a program through Windows Firewall link on left tasks pane.
In “Windows Firewall”, click the Exceptions tab, and then click Add Program.
In the “Add a Program” window, click Browse button.
Click the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe executable program, click Open button. MSSQL.1 with is a placeholder for the instance ID that is obtained from previous procedure. Note that the path may be different depending on where SQL Server 2005 is installed.
Click OK button.
Repeat steps 1 through 5 for each instance of SQL Server 2005 that needs an exception.
For SQL Server Browser service, locate the C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe executable program, and click Open button.
Click OK button. -
Solution Manager 4.0 & SQL Server 2005
I see in the documentation the step to install SQL Server 2005 with the 850 character set. If I want to add the solution manager database to an existing instance (which uses the default char set), but give the database itself the 850 character set...will this cause an issue. I have read some posts where this causes issues for other SAP products...but have not read anything specific to solution manager. If this does cause issues, are there any workarounds, other than creating a new instance, changing the default char set for the entire instance, or finding a new db server?
Dear John,
unfortunately there is no other solution. To ensure, that the database can work correctly it is necessary, that the SQL Server installation as well as all databases within the instance have the same collation. For new installations the SAP installation tools automatically use BIN2 as this will ensure compatibility with unicode. To find out which collation is installed for the server instance you can use the following query:
select serverproperty('collation')
To find out the collation of a specific database you need to execute the following query:
select databasepropertyex('<db-name>', 'collation')
The fact that the database collation and the server collation must match has nothing to do with the installed SAP Product - the two collations need to be the same in any case.
Please read SAP Note #600027 to find the necessary procedure for changing the server / database collation,
hope this information helps you,
kind regards,
beate -
Business Objects XI 3.1 using SQL Server 2005 SP3
Hi,
I've searched and googled and can't find a definitive answer to this question: I'm looking to move to BOXI 3.1 and am checking compatibility with our systems. The 3.1 Supported Platforms doc lists SQL Server 2005 RTM/SP1/SP2 as compatible, but I cannot find out whether SP3 is! I assume not, but the Supported Platforms doc is dated before the release of SP3- does anyone know whether SP3 will work and/or the document will be updated?
Thanks for your help!
TomMost likely it will work just fine. As supported platforms documents were released prior to SP3 release, they cannot be changed.
With new SP Supported platforms will have MS SQL2005 SP3 record in them.
What this means - product weas not tested with SQL2005 SP3, so we cannot guarantee that there are no issues. -
JDBC Connectivity for SQL Server 2005 Windows Authentication Mode
Hi Everyone,
In my Scenario we are using SQL Server 2005 with Mixed Mode Authentication. Now we are planning to move only with Windows Authentication Mode.
We have configured DB with Window authentication mode & user id have been configured in PI channels however we are getting error. We checked microsoft site, which says Windows Authentication mode DB can not be connected using JDBC drivers.
http://support.microsoft.com/kb/313100
In this above link see Basic Connectivity Troubleshooting Section.
Please let me know if someone confirued JDBC Channel Successfuly with Windows Authentication Mode.
Thanks In Advance
Regards,
Bharathi.I think this issue is related to the way that Vista, Windows 7 and Windows 2008 / 2008 R2 treat users who are logged on to the system with an account that is a member of the local administrators group when SQL is running locally.
If your SQL setup has left you with BUILTIN\Administrators being a member of the sysadmin server role and you start up SQL Management Studio you'd expect to be mapped to the sysadmin role if your user account is in the local administrators group, however
these OS disable this ability and when you try to connect to the database engine SQL server doesn't know you are a member of the local administrators group.
To get round this, close all your open SQL management studio windows and then start a new window by right clicking the icon in the start menu and chosing to run as administrator. This time when you try to connect to the SQL database engine, windows doesn't
"hide" the fact that you are an administrator. If you need to do this a lot you can go to the compatibility tab on the properties of the shortcut and set it to always run as administrator.
Alternatively you can install the admin tools remotely and you don't get this effect.
Tim -
BPC 5.1 SP11 with SQL SERVER 2005 SP3
Hi all,
i have a BPC 5.1 SP11 single-server installation.
I know the DB Server prerequisite is Microsoft SQL Server 2005 SP2 and cumulative update package 8.
SQL Server 2005 SP3 is supported?
is there any document about compatibility?
have i install SP3 before or after BPC Installation?
thanksHI Paolo,
SQL Server 2005 SP3 is supported with SAP BPC 5.1 SP3 or any other later version.
We already installed for few customers SP3 and this patch fix bugs into SSAS and also improve some performances regarding SSAS.
So the recommendation will be to apply this patch in your environment because it will bring just benefits.
If you have multiserver installation remmeber that you have to apply the patch in all servers not just into Database server.
Regards
Sorin Radulescu -
Does anyone know if there is a flag I can use to prevent a SQL Server 2005 database from being upgraded to SQL 2014 when it is restored to a 2014 instance?
Don't ask why, I just need to know if this is possible or if 2005/8 DB's are required to be upgraded if they are going to run on SQL 2012/2014 instances. The documentation seems to say this is so, I just want to verify that.First: You cannot directly restore a 2005 database to
2014. MS supports migration over 3 SQL Server version steps; means you can restore 2005 to 2008/2008R2/2012, but not to 2014. You have to do a migration step between.
Olaf I was looking for this today, because I'm working with a new customer that have SQL 2005 and I have SQL 2014. And needed to restore a backup form the production server in my test server.
When I read what you write I think, oh no!! I have to install SQL 2012 in my server. But that it's not an option for me, and I say let me try to restore the DB first in 2014 and if not work install 2012.
You can restore a 2005 database to 2014 directly, and it works.
For reference the version number in the servers 2005 (9.0.4035 SP3) and 2014 (12.0.2000 RTM)
This is not related in any way to the original question that you answered (the file format will be upgraded to the new motor, that is sure).
I put this lines because in the future there will be some people searching about if possible to restore a 2005 DB to 2014, and like me will read your lines and think it's not possible and that can make a decision to buy 2012 and not 2014 to that new server they
will migrate.
Don't forget to mark the best replies as answers!
Maybe you are looking for
-
Balance Carry Forward to new fiscal year wrongly
Dear All, Currently we are in 2012 fiscal year. our fiscal year starts form July to June. The problem is user has posted some of the documents in 2010 fiscal year 13th period after Changed the G/L account on 24.05.2010 (2010 Fiscal year) fro
-
Passing errors back to Source system in proxy in Sync communtion
Hello Experts, I am developing a Sync Proxy-JDBC scenario. It works perfectly fine. In case if there is any error while delivering the data to JDBC receiver, we see error in SXMB_MONI in PI but can we pass same error to Source? i tried to use fault d
-
Hi Guys Am looking to get the Nokia E65 but want to check it pairs with my cars bluetooth system. (BMW 330ci 2004) Anyone tried this combo ? Do contacts synch also ? Cheers
-
Unwanted e mail from apple Support communities
Hi. I recently asked a question on here and found the newer very good and I find a lot of help. Now this request might seem daft after saying that but please can you tell me how I stop the answers to other questions because I am getting up to 20 a d
-
I now have a problem to stop oc4j using bat file(stopinst.bat) provides with Oracle 9IDS.It returns me this error: "security error: invalid username/password for default(admin)" and don't shutdown oc4j. What can i do? Thanks for your answers.