I have Power Pivot with data sourced from MS Access Table. The Data in MS Access changes every day. But we want the Power Pivot model data to be static. i.e. it must not get updated when refreshed.
The Excel file is saved for future reference as back up & every day new Excel file is created with fresh data.
Want to Remove Link because, if i press refresh in back up file i don't want to fetch the latest data in that file.
I want the data in the Model without connection to MS Access. (Same as remove external link in Excel sheet & keeping the data.)
earlier i tried to find if there is some functionality similar to remove links, but could not find.
Related
I currently have a package that creates an excel spreadsheet with multiple tabs, and it names each column in each tab. Later in the package, I have excel connections that select my data using queries and populates each column in each tab based on the mappings I define. This has worked for a long time, but since a driver update, my OLE DB connections wont let me create the excel spreadsheet anymore. The key here is that the package needs to be able to be called by a scheduling system and be totally hands off and self sufficient. Also, the excel spreadsheet is created brand new with every execution of the package so we can keep an archive of old reports.
I've tried to use the existing excel connections to also build the spreadsheet, but I don't see a way to populate multiple tabs in the same spreadsheet with excel connections.
Is there a better way to do this without having to do a C# script.
I added a source in PowerQuery via ODBC to Azure, pulling data in free form query. On top of that I designed few new columns & measures in PowerBI and created report.
All good until I want to add some more columns in the free form query. My issue is:
1. If I proceed to edit the query via editing from inside Advanced Editor, it's going to take longer time & error prone as well; testing & retesting until the query is properly written.
2. Delete the existing source, add new Spark SQL query and run it without hassle. But then, create all the existing measures & columns again in PowerBI.
I don't see any other way to edit the same existing source in a hassle free way and retain my measures & columns of PowerBI intact.
Any pointers will be helpful.Thanks!
I got the idea; guess I haven't had considered the editing of Source of the query; screenshot attached.
So I have an excel spreadsheet with Product and Notes. I'd like to import this information into SQL and everytime people enter more products and notes into this excel sheet, it will automatically updated to the new one whenever I run the syntax?
I finished creating Product - Notes, which I imported current data into that table.I was planning to use insert into function, and every day insert the new values in the table. But this seems too manual.
Is there a way i can do this? The excel spreadsheet is updated daily.
I'm using SQL Server 2008
I'm sure this is possible. You could have the excel connect to your database and then write some macros to save the data to the table when there are changes or new rows are written.
It would not be easy. There is a lot of complicated logic here and excel was not written to be a front end for a database.
I believe the time spent changing your spreadsheet to work this way would be better spent actually writing a client server application to modify the database using a web application or a local application. Client server front end applications are easy to write these days with lots of examples, tools and templates. For someone with experience a simple data entry / modification form is just a couple of days work for a robust application.
Changing the excel file would be much harder.
You could use SSIS to import the excel data into your database on a scheduled basis.
This isn't a coding question, so much as it is a functionality question.
I'm a bit new to Powerpivot and I'm attempting to use Powerpivot as a way to deliver reports to my team rather than SSRS because in our company, the only SSRS ReportServer I can use is officially "owned" by a team that is hostile to my team.
I have written numerous SQL ad-hoc queries that we are using for reports in SSRS, but been I've trying to migrate them to Powerpivot. For some of the reports, I've been able to paste the SQL query into the powerpivot window and make a pivottable out of these. However, I'd like to be able have some workbooks just contain the results of the query (they don't deal with numbers, as some of them are a data dump or a large collection of text strings), so that they look like the powerpivot window's dataset, but that they can be filtered, sorted, etc. Is this possible, or can I only use pivottables? I can't seem to find a way that I can just get Excel to directly display what is in the Powerpivot window without pivoting it - I know it is called Power*pivot* but because the PP window just shows the query results itself, I'm hoping there is a way to use it as an alternative to SSRS.
Also is there anyway to check if our Sharepoint server is capable of running Powerpivot so that I can deploy reports there for users to use without having Powerpivot installed on their computers other than by saving it to Sharepoint and seeing if a user can run it? If not, how difficult would it be to have an IT team update the SP server so that it can handle PP?
Any help is appreciated, as I'm in a position where I cannot contact IT or project management, and I can't raise any red flags with IT/BI/PM. Thank you very much for your time.
It sounds like you just want to get the results of your SQL query directly into an Excel spreadsheet, where you can use the Excel filter and sort capability. It doesn't appear that you want to use any of the functionality that PowerPivot provides, so you can achieve what you described by using an existing Excel component, Microsoft Query. It's a bit of a clunky old interface but it works. Here's some instructions to use:
In an Excel spreadsheet, click on the Data tab, select the "From Other Sources" button on the Get External Data area of the ribbon.
Select "From Microsoft Query"
On the "Choose Data Source" click OK to create a new data source
On the "Create new data source" window select the appropriate driver and database details for your data source
If using a SQL Server data source, don't select anything for the optional step 4 (select a default table).
Click OK to return to the Choose Data Source window, then OK again to select the new data source.
You're now prompted to choose columns for your query, but if you already have some SQL then click Cancel - this will display a prompt to continue editing in Microsoft Query - click Yes.
The Add Tables window pops up, click Close
You're now in the Microsoft Query interface. If you click on the SQL button, you can paste in your SQL. Click the Return Data button to run the query, the results will be displayed in an Excel worksheet.
Once this is set up, you just need to click "Refresh Data" on the Data tab to re-run the query and update the spreadsheet.
I have an .mdb file, which is used as a data storage by one particular application. The application itself does not have tools to insert large amounts of data, and I need to insert around 300-400 generated records.
How can this be accomplished without using VB? (since I know nothing about it)
At first I thought that writing a procedure, but from what I can tell Access does not support procedures and functions (which ir really weird), only basic SQL statements.
Is exporting data into other DB like Postgre, writing and running a procedure there, and importing the data back into .mdb file possible? Or there are other solutions?
If you're looking to export data from a specific table then select that table and right click on it. A menu will appear that allows you to export the contents of that specific table. Choose the format (probably .csv or .txt for max flexibility) and then import it whereever and manipulate it accordingly.
If you want to reimport your results then choose from the File -> Get External Data -> Import menu and import your newly manipulated data. That should do it. Just make sure that the data columns align properly with the table your importing into. This shouldn't require any VBA. This advice is pertinent to Access 2003.