I'm currently in the process of coming up with our upgrade plan for our migration from SQL Server 2005 to SQL Server 2012, and some of our business units still use ProClarity.
I'm aware that this is essentially a "dead" application; where Microsoft isn't upgrading it anymore, and it's scheduled to be EOL'ed in the future.
After googling and digging around on Microsoft's forums, I still can't come up with a definitive answer as to whether the 2012 upgrade will be incompatible with Proclarity. (Business users are on 6.2; which is one minor revision behind)
Has anybody tried this out and been successful? Would we need to keep this portion of the BI tools on SQL Server 2008?
Upgrade was successful, and the users were able to connect to 2012 Analysis Services using ProClarity
Related
I've been doing this for 3 days. I couldn't find the solution. Normally it was supposed to have features like the following.
What is the cause of this problem? And how do I solve it?
You're using SQL Server Express. SQL Server Express is a very cut down version of SQL Server and does not provide anywhere near as many features as Standard and Enterprise; such as database mail (Additional Database Services). If you need features, you need to purchase SQL Server and pay for the edition licences that have the features you need.
If you are using SQL Server for development purposes only, you can use SQL Server Developer Edition, which is allowed to be used for non-production environments only. Developer edition has all of the features that Enterprise does.
You can find the full list of features supplied by each edition here: Editions and supported features of SQL Server 2017
I am currently running SQL Server 2005 Standard Edition on a Windows 2003 server machine.
I have gone to the properties of the server and confirmed that the Login Auditing is set to both failed and successful logins. For some reason though there is nothing in the logins for fails or successes in the SQL Server logs when I know there have been logins for both.
I have searched out the reason for this and have not been able to come up with anything helpful, so I am hoping that someone here could give me a little direction. This is working on my other SQL Servers, so I know where to look for the results, but there are none there.
After speaking with Microsoft about the issue and doing much research, it was determined that this was an issue with the particular version of SQL (SQL Server 2005 Service Pack 2 9.00.3042) running on that particular version of the windows release. We reinstalled SQL, and then did all the updates and patches to both windows and SQL and this seems to have resolved the issue. The SQL logs are now tracking both success and failed logins.
I've been trying to work out whether it's possible to manage (i.e. add tables, modify them, create stored procedures) a SQL Azure database using some kind of GUI like SSMS and I keep coming up against different answers.
I found a post from the end of 2009 saying that it would be supported in SSMS but I'm not sure if that includes the Express version? Does anybody know what the most recent update of the express version is and whether it supports it?
I think I'm right in saying that it can't be done in Visual Web Developer 2010 (and I can't afford the full fat VS2010).
I'm prepared to consider alternatives though if anybody knows any full features GUI tools that work with SQL azure and I don't mind paying for a commercial license if it's not too expensive.
Thanks.
Yes, SQL Server 2008 R2's Management Studio does support working with SQL Azure databases.
See:
Getting Started with SQL Azure Development
There are a couple of options
1) You can use SSMS (get the free version by downloading SQL Express v2008 or greater) with advanced services. This will give you SSMS. You can then connect to SQL Azure using SSMS. However - there is a limited set of functionality available via this tool.
2) You can use SSDT (stand-alone for free) or from within VS2010 SP1 or greater. Again, you can connect to SQL Azure, but there are some restrictions on what you can do.
I am using the SQL Express on AWS RDS (free usage tier) myself lately (and connecting via SSMS or SSDT). I prefer their implementation of SQL Server in the cloud to Microsoft's implementation of SQL Azure.
I'm having problems setting up the database described in Apress's Pro Business Applications with Silverlight 4. I have SQL Server 2008 R2 Express which doesn't support Full Text Search, and I can't install the database from codeplex (AdventureWorks2008 OLTP) because it requires Full Text Search. The book suggests getting this exact version of SQL Server (Express and everything). I'm just wondering if anyone knows of a way to install a database into SQL Server when a feature is not provided. Is there anything else I can do. I'm stuck for the time being.
Thanks.
SQL Server 2008 R2 Express with Advanced Services supports full text searching - you probably don't have that version.
http://www.microsoft.com/express/Database/InstallOptions.aspx
I have a reporting services project with lots of reports developed in SQL server business intelligence development studio that comes with sql server 2008. I want to deploy these reports to a server that has reporting services 2005 only but the deployment is failing. I'm wondering if any one around here has been able to deploy reports developed in business intelligence development studio 2008 to a server running reporting services 2005 only.
If it isn't passible, is there a way of downgrading my report project back to reporting services 2005 so i can be able to deploy my reports?.
Unfortunately this is not currently possible.
The following thread contains a discussion from the MSDN forums pertaining to a similar query. If you read through it, you will discover that an MVP raised this as a development/support request with Mcrosoft.
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/686cac48-bc14-4978-b7bf-acbc0c90384e/
Is it really that bad?
For going from 2005 -> 2000, you just had to strip a couple of lines of xml out of the rdl file.
Can't you do something similar? Assuming you don't use 08 specific things like Tablix
?
Microsoft, you don't know how huge of a pain in the butt this problem is. And we're left to find out about this incompatibility only after creating reports in VS 2008 and trying to run them on SQL Server 2005.
This is extremely poor product management on Microsoft's part.