Can I downgrade from SSAS to PowerPivot in excel 2013?
Reason being - I have 64 bit excel installed on my machine but my SSDT is VS 2012 shell 32 bit.
Its really slow on VS 2012. I have no control of how software to be installed on my machine and have been passed on this laptop so I dont have much choice actually.
Can anyone please guide me how to do this?
Thak you.
Peddie
If you want to use PowerPivot you have to install Excel. PowerPivot is an Excel add-in.
Now, SSDT only comes in a 32-bit version, there is no 64-bit version to install. Even if it were available you'd probably wouldn't see any performance improvement in your case because the data model is not actually "processed" by SSDT. You build in SSDT and then deploy to a SSAS server in tabular mode. If the model you build is slow it could be because a lot of reasons, one of them being that the SSAS server your deploying to is running on your local machine.
If you want to move your data model from SSAS to PowerPivot, try this http://blog.gbrueckl.at/2014/05/restoring-a-ssas-tabular-model-to-power-pivot/.
It involves taking a backup of your tabular model and then restore that in PowerPivot. It's worked for me in the past.
Related
i m trying to upgrade ssis 2008 packages with c# architecture (screenshot joined), to ssis 2016 for moving to the cloud, i ve seen similar questions but the few answers there are do not apply when i try them, especially not this link: https://learn.microsoft.com/en-us/sql/integration-services/install-windows/upgrade-integration-services-packages-using-the-ssis-package-upgrade-wizard?view=sql-server-ver15 the wizard dont list my 2008 packages when i run it, after importing em on a new 2016 solution, and it doen trun automatically,
do you have a tested way to upgrade 2008 packages with the above format?
currently i m trying bimlStudio, seems to be a lead, didn t figure it out yet,
thank you,
I currently have a ETL system running on SQL Server 2014, it used to be using individual package deployment method. We recently changed it to use the new SSISDB project deployment method.
The issue is these same packages with no other changes take roughly twice as long as the old deployment method. I understand a lot of overhead may have been from the logging that is set to 'Basic' by default for project deployments. I changed that to none with some improvement, but still far slower than our old deployment model, or even running the packages locally in visual studio.
Based on my research this is because 'None' still logs quite a bit of information to SSISDB which is causing a huge overhead. Previously we only logged errors by email with the Package Deployment Model, but with the Project Deployment Model that is not the case, and as I understand I cannot log less information in Sql Server 2014 when using this deployment model, as custom logging was only introduced in 2016.
Has anyone else had this issue and come up with any solution? Preferably a solution that isn't "switch back to Package Deployment Model" or to upgrade to 2016 which will not be in the near future. Currently I have tried and index on internal.executables from the SSISDB database. referencing this article http://www.argento-it.co.uk/ssis/ssisdb-slow/
This did not improve the situation at all, with the run time remaining the same
I installed SQL Server 2014 Express. It doesn't have SSIS, so I installed SQL Server 2014 evaluation. I still don't see SSIS. Am I installing it in a wrong way or does SSIS come only with purchased SQL Server 2014 Standard edition and above.
I need to load multiple flat files into a database so I can work on them together.
Express version comes without SSIS. Actually there is not free version of SSIS. You need either SQL Server Standard, Developer, or Enterprise edition to get access to BIDS. If you have Visual Studio then you can download SQL Server Data Tools and you will be able to create SSIS projects
if you have Visual Studio 2013, then download and install this: http://www.microsoft.com/en-us/download/details.aspx?id=42313
SSIS is only available in the Enterprise, Business Intelligence and Standard editions. It should be available in the evaluation though as the evaluation is based on the Enterprise version (with a 180-day trial time).
It might be that you have to explicitly select to install the component (I haven't used the trial version in many years and honestly don't remember).
See this for more information: Features Supported by the Editions of SQL Server 2014
SSIS comes with SQL Server Developer edition which is inexpensive. Developer comes with all the features of Enterprise I believe.
SSIS IS NOT FREE !! We have to buy atleast the standard edition of Sql Server which is too costly if you are working for a small company.
Best way to load multiple files into a database without SSIS is to merge all files with same columns together in excel Merging files
and then load that big file into the database using Sql Server Import & Export.
Formatting columns may be tricky.
VS 2012 has an excellent support for comparing database projects and databases.
I'm wondering if there is a standalone version for the respective software to use on a deployment machine - or some other way to use it without having to install the whole of visual studio.
You can install just the SSDT for SQL Project bits on a machine. That does not require a full install of either Visual Studio or SQL Server. You can generally keep an eye on the SSDT Blog for the latest release news. You can find that at: http://blogs.msdn.com/b/ssdt/
At this time, the most recent release is the October 2013 release.
As noted in the various articles, you may need to make an Administrative Install Point if your target machine does not have internet access. Follow the instructions in the article and you should be fine.
I've written some articles about this on my blog at http://schottsql.blogspot.com if you look up the label for SSDT.
Basic Question -
I have installed SQL Server Express 2008 with integrated SP1. This is the database engine alone.
I realise now that I also need the express studio in order to perform a few tasks. I have installed it, however I know that it was the original installer from before SP1 was released.
I have tried it and it appears to work fine but should I install SP1 / could something unforeseen happen in the future?
Some background! -
I wrote out the question and just realised that people probably don't care, so I just summed it up above!
After reading many different sites and guides, the install order for Visual Studio 2008 really confused me.
I really wanted to install SQL Server Express 2008 with advanced services, however on my other machine I had so many problems with it not being detected with Visual Studio, I just wanted an easy life!
I found the download from Microsoft that had SQL Server Express 2008 with SP1 integrated, however it was only the basic engine without any addons. (At the end of the day, as much as I wouldn't mind reporting services, I doubt I will need to use it any time soon).
I installed this, and after applying the hotfix (for x64 sql) my Visual studio can detect and use it no problem.
Now, I want to use Management Studio Express to write a few SQL scripts. The installer is obviously the original one. It seems to work fine, but I cannot find out any information - do I need to install SP1 for it?
Just install it, if its found something it can update - it will, if not... it won't....
Thanks to the wonder of Windows Installer (and I don't mean "I wonder why it's doing that?"--I mean like "This is wonderful!") it is unlikely that you have caused any big issues by running the older version afterwards.
So, yeah, you can probably just install the SQL 2008 Express Management Tools with no worries. If you want to be sure, afterwards just run the SP1 installer and it will make sure everything's up-to-date.
I always make sure to apply patches to client tools as well as server services. There is no reason to take the chance that your client tools have fallen behind in servicing.