Breeze with SQL Server 2005

Hi,
it seems that MS SQL Server 2000 isnt available anymore - SQL
Server 2005 is out.
Runs Breeze with SQL Server 2005 also?
thanks

Hi Dav:
SQL Server 2005 won't be officially supported until the next
release
of Breeze, which is expected to ship sometime in the fall.
Hope this helps!
Jeff Von Ward
Breeze Product Support Manager
Adobe Systems, Inc.
On Sat, 1 Jul 2006 12:34:37 +0000 (UTC), "DavHo"
<[email protected]> wrote:
>Hi,
>
>it seems that MS SQL Server 2000 isnt available anymore -
SQL Server 2005 is out.
>Runs Breeze with SQL Server 2005 also?
>
>thanks

Similar Messages

Crystal Report 8.5 with SQL SERVER 2005 problems

Post Author: AREVA
CA Forum: Data Connectivity and SQL
Hi All !We have some problems with Crystal Reports version 8.5 with SQL Server 2005: 1) When we want to generate a report (using data in SQL Server 2005) we have a popup message error : "impossible to loaded pdssql.dll".2) If we want to use SQL Server 2005, which Crystal Reports version we must used ? Is there any restrictions with this connectivity with 8.5 version ?Please, let me known, all informations about SQL Server 2005 and Crystal Report 8.5.Thanks for all !Best regards Anthony

Hello Kamlesh,
There is no expectation that the ActiveX viewer (RDC?) from CR8.5 will work in any version of Visual Studio .NET. There is also no expectation that the ActiveX viewer from CR8.5 will work on a machine with a 64 bit operating system.
You're using VS2008. You should migrate to the bundled edition of CR for VS2008 (v10.5), the ReportDocument object, and the .NET Windows form viewer or Web form viewer.
Sincerely,
Dan Kelleher

Error While Installing IDES ECC6 with SQL Server 2005

Dear Experts,
I found an error while installing IDES ECC6 with SQL Server 2005. The error is raising at the stage of 17 of 24 processing the procedure of 195 of 197 (sap_z_set_permissions).
I have tried several times by configuring different type of activites but still i am facing the same problem at the same stage. Please help me in thig regard.
I herewith pasted hereunder log files information
Regards,
B.Sudharsan
ERROR 2008-01-17 18:38:47
FCO-00011 The step ExeProcs with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs was executed with status ERROR .
INFO 2008-01-17 18:40:05
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs".
ERROR 2008-01-17 18:38:47
MDB-05053 Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.

Sudarshan,
Occasionally, mid-way through the upgrade, DB permissions to users might change. Check to see, if the users SAP<SID>, OPS$ users have the DBA privilege. Re-assign the role and try continuing with the upgrade.

ODI 10.1.3.5 with SQL Server 2005

Good afternoon,
We recently installed 10.1.3.5, in a Windows environment with SQL Server 2005 and Hyperion Essbase/Planning/HFM 11.1.1. We were following John Goodwin's infamous blog (thanks, John!), but ran into a number of snags.
For instance, when we set-up interfaces with flat files as the source, loading metadata either to Planning or Essbase, ODI errors out when:
1) our header name in the flat file has spaces (using double quotes didn't work)
2) our header name in the flat file is different than the reverse property name from Essbase/Planning.
Also, we're now seeing an issue in our Flat file to Essbase metadata interface where the SQL used in the IKM seems to be incorrect. Below is the error message we're receiving:
"org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 20, in ?
com.microsoft.sqlserver.jdbc.SQLServerException: An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements,
look for empty alias names. Aliases defined as "" or [] are not allowed. Add a name or single space as the alias name."
We are thinking that the culprit may be either the wrong .jar or .jre we're using with SQL Server 2005, as there seem to be inherent issues with the SQL generated in the LKM and IKM. Our questions to you:
1. What sqljdbc.jar driver version are you using?
2. What .jre version are you using?
3. What environment does the above work correctly in? (perhaps an earlier version of ODI against an earlier version of Hyperion?)
FYI - We have tried sqljdbc 1.0 and 2.0, with .jre 1.6.0_10.
Thanks in advance!
-O
Edited by: Alapat on Jan 22, 2009 8:04 AM

Thank you very much for responding!
After a 2 week battle, we are now finally coming to a close on our issues (although we cannot say for sure what all of the causes were).
Here is what we discovered about our questions, through other threads:
1. John Goodwin was using JRE 1.6.x, so we ruled that out as a culprit.
2. Others are using SQL Server 2005 just fine with ODI, so we ruled this out too. We chose to keep the sqljdbc 2.0 driver.
Here are some issues we did uncover during our investigation:
1. We were having issues with our agent, specifically regarding the HFM technology. We created a new one, added a few extra parameters, compiled the agent, and are now back up and running. We realized the problem when we switched to "Local (No Agent)" and saw that we were not having as many issues.
2. We went into the physical agent and pressed "Update Scheduling". We do not know if this had any effect, but we suddenly noticed that our flat file header issues were resolved.
3. The Essbase issue was due to a configuration error with our Hyperion Essbase physical technology. We went into that technology and changed a setting on the "Languages" tab, called "Object Delimiter". It had double-quotes in it - we removed that parameter and instantly saw a change in the SQL being executed.
4. Some of the mappings in our interfaces needed to be executed on different environments. i.e. - We needed to switch to "staging" when the flat file header was different than the target column name. Newbie mistake - we thought ODI had built-in intelligence to choose correctly for us.
5. When doing a reverse on Essbase models, we noticed that the Essbase columns would populate with an "Undefined" datatype, instead of the expected CHAR. We have to manually define all column datatypes after every Essbase reverse now. Must be a bug.
6. We also noticed when doing a flat file reverse that all columns auto-populate with datatype STRING, length 50. We have to manually personalize that option for different Hyperion applications, based on need. i.e. - some require numeric datatypes, or smaller/larger lengths. This was obviously a newbie error. :)
Thank you for your tip on the MS SS2005 JDBC drivers - we will look into your other options - IMHO, JTDS, etc.
-O

Am failing to install Java IDM in a Windows XP machine with SQL Server 2005

Hi,
I am new to Java IDM . I had downloaded IDM 7.0 and trying to install. But i am failing to install Java IDM in a Windows XP machine with SQL Server 2005.
I used .,
JDK 1.5
Tomcat 6.0
Microsoft SQL Server 2005
Microsoft SQL Server 2005 JDBC driver
I got the following error while trying to connect the waveset database with Repository type as SQL Server 2005(JDBC Driver)
com.waveset.util.ConfigurationError:
==> com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'waveset'. The user is not associated with a trusted SQL Server connection.
what name i can specify in JDBC ... is there any need to create DSN for that ...........
The Parameters that I have given for connection are:
URL: jdbc:sqlserver :1433;DatabaseName=
JDBC Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
Connect as User:
Connect Password:

Do you have your SQL server set to Windows Authentication mode only?
You should change it to allow mixed authentication. You can do this in SQL Server Management Studio under Server Properties -> Security.

Integrate Oracle IDM with Sql Server 2005

Hi Guys,
We maintain the employees information in Oracle IDM and we want to integrate Oracle IDM with Sql server 2005.
how we can this.

The DB connector?
The 9.0.1.4 version supports SQL server 2005.
The latest version of the GTC db connector might also work.
Best regards
/Martin

Open (.sdf) file with SQL server 2005 Management Studio

In VS2005, I have created a SQL Mobile database, (.sdf).
Copied that (.sdf) file to Desktop, and when I try to open with SQL Server 2005 management studio, its showing error "make sure the application for the file type (.sdf) is installed."
How can I open this file with SQL server?
Regards
Abinash

You must install SP2 if using Management Studio Express (http://www.microsoft.com/downloads/details.aspx?familyid=6053C6F8-82C8-479C-B25B-9ACA13141C9E&displaylang=en)Erik Ejlskov Jensen, MCTS: WM App, MCITP: SQL 2008 Dev - http://erikej.blogspot.com
Please mark as answer, if this was it.

EPM 11 Configuration with SQL Server 2005

Hello,
I am having a terrible time trying to get the EPM System Configurer to communicate with SQL Server 2005 Evalution. I keep getting the error "Cannot open database "server" requested by the login. The login failed." I have the windows firewall turned off. The protocol TCPIP is turned on and other protocal are turned off. Any suggestions. Thanks in advance.

As John mentioned it is supposed to be supported in a future release. That version would be 11.2 -- there will be a version coming out before 11.2 and it will not support 2008.
Regards,
John A. Booth
http://www.metavero.com

TopLink with SQL Server 2005

Could someone help answer this question:
Has TopLink 10.1.3.x been certified to support SQL Server 2005?
I appreciate your information.
Haiwei

It is certified on SQL Server 2000.
I know some customers are using it with SQL Server 2005, though.

How can I connect NetBeans 6.1 with SQL Server 2005?

Hello guys...
how can i connect NetBeans 6.1 with SQL Server 2005?
there is no SQL Server in Server list when we create a new Web Project and choose Server.
I'm new to NetBeans and this is my first time of posting.
If has some errors and unwanted disturbing,pls understand me. Thanks.
(If you have references or some snippets, i'll be glad if u can share.)
scsfdev

The JDBC-ODBC bridge wasn't recognizing any of the primary keys I had set up in SQL Server. After lots of head banging, here's the solution I came up with:
1. Download the appropriate driver. SQL Server 2000 requires the SQL Server 2000 JDBC driver (http://www.microsoft.com/downloads/details.aspx?FamilyId=07287B11-0502-461A-B138-2AA54BFDC03A&displaylang=en).
SQL Server 2005 download: (http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794-950D-81E1EC91C1BA&displaylang=en)
3. After installing, right-click on "Libraries" in your project, and choose "Add Library...". Next, give it a name (i.e. SQLServer2000), and select "Class Libraries".
4. On the next screen, find the JAR files (should be in C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\), and add them under the "Classpath" tab. It will now be available under "Libraries" for future projects.
5. You can now create a connection to a specific database under the "Services" tab (next to "Projects" and "Files" in the top left of the screen). Select "Microsoft Sql Server 2000 (Microsoft Driver)" and format the "Database URL" like this:
jdbc:microsoft:sqlserver//YOURSERVER:1433;DatabaseName=YOURDATABASE
1433 is the default port, though your DBA may have changed it.
I posted a simpler version of this on the NetBeans.org FAQ page - they had the following title with no content on the answer page:
"Cannot Select Tables From MsSql 2000 Because It Says No Primary Key Next To Each Table But The Tables DO Have A Primary Key. What Do I Do?"

B1 with SQL Server 2008 and SEC with SQL Server 2005

Hi,
we are currently upgrading from B1 2005 to B1 2007. With B1 2007 we could use MS SQL Server 2008. In parallel we have a SEC implementation (which uses SQL Server 2005).
Would there be any issues with the integration of B1 and SEC although they run on with different SQL Server products?
Thanks
Olaf

Hi
By creating two different instances you can run both simultaneouly. But pls do check whether SEC will run on 2008 or not ?
Ashish Gupte

App not versioned error in JDeveloper - ADF with SQL Server 2005

Hello All,
I am developing a sample ADF application. Database is MS SQL Server 2005 SP2. I get below error message. I am trying in parallel to google it... However trying here if any encountered such an issue and had resolved it.
Thanks in advance for your time.
Cheers,
Vagic.
[02:06:19 PM] Deploying Application...
<Feb 23, 2010 2:06:20 PM PST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application ExmReports is not versioned.>
<Feb 23, 2010 2:06:20 PM PST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1266962779600' for task '0'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)

You might need to add the JDBC jar file for SQL Server to the classpath of the integrated WebLogic. See minute 8 here: http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/NBtoJDevProject/NBtoJDevProject.html

Installation of ODI with SQL Server 2005

Hi
I am trying to install ODI with MS Sql Server 2005.
I created a database in Sql Server & created a user with db_owner rights for logging into the database.
While trying to install Master Repository, i selected Sql Server with following details
Driver: com.microsoft.jdbc.sqlserver.SQLServerDriver
URL: jdbc:microsoft:sqlserver://<myhostname>:1433;SelectMethod=cursor
The repository does not get created giving error:
*com.sunopsis.core.q: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 1 (""): Data type 0x38 is unknown*
Now if i change the URL to jdbc:microsoft:sqlserver://<myhostname>:1433, the repository gets created successfully. But at the time of login into the topology manager using the same Master repository, it again prompts me the same error.
Has anyone faced the same issue?

Hi,
You are using SQL server 2005 but trying to connect using the SQL server 2000 connection details you should be using
com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc:sqlserver://ServerName:1433;databaseName=DBNAME;SelectMethod=cursor
You will also need to make sure you are using the correct SQL server 2005 driver, if you are using a version of Java before 1.5 for ODI then you will need the SQL Server 2005 1.2 JDBC driver.
Cheers
John
http://john-goodwin.blogspot.com/

Installing SAP R/3 with SQL Server 2005..

Hi,
Microsoft is about to release "SQL 2005" in Nov05. Has anybody in here thought of installing/upgrading SAP on MS-SQL's latest version of the database server. On doing some research on the net I noticed that Microsoft has already upgraded their SAP R/3 environment to the beta edition of SQL Server 2005. I did not find any information on SAP having certified SQL Server 2005 yet.
Do we have to wait till ECC6.0 or whatever the new version of ECC would be to leverage the SQL Server 2005 D/b ?
Any thoughts/information on the readiness of SQL Server 2005 for SAP R/3 would be appreciated.
Jay

Hi Jay,
Past experience says SAP won't support a new platform (e.g. DB, OS, etc) until they have had a chance to test it. Your official SAP document for what is supported is in the Product Availability Matrix. http://service.sap.com/pam
With that said, that doesn't mean that you can't try it out. Of course not in a test environment. You get some very good learning experiences from trying. But don't enter a customer message about a non supported platform.
Good luck,
John

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.

Breeze with SQL Server 2005

Similar Messages

Maybe you are looking for