I'm currently using an execute sql task in SSDT that queries AD. Here's what I have:
< LDAP://ou=groups,dc=blahblah, dc=com>;
(|(cn=*_BI_*)(cn=*.BI.*));
cn
The results eventually write to a table. In the table, I'm getting results for names such as AS_BI_Core, IS_BI_App, and anything that has an underscore. I'm not getting any results for the .BI. cn which is what confuses me. If I do a custom search using active directory users and computers for (|(cn=.BI.)) I get 6 results that are not showing up in the table that I'm writing to. Does anyone know why this would be?
Related
I've been tasked with converting one of our old Access queries from pointing to SQL Server to point to DB2. The query is essentially the same outside of it pointing to 3 new linked DB2 views.
The query has 4 criteria in it. 3 of the 4 are either string or number columns (those work fine). The issue I am running into is for the 4th field which is a Date field.
Anytime I try to run the query with any date Criteria like > #2017/10/27# in the date field, it doesn't work and I get this strange message:
What makes this even more strange is when I change the criteria to a parameter to prompt for a date input, IT WORKS. I would appreciate any help or work-around to solve this issue.
Note: I am on 64-bit Access
My machine is on 64-Bit, but after testing the Access Database query on 32-Bit, it works now.
so i am trying to pass time during the end of the world learning a bit of access (i already know a decent bit of sql). I am particularly interested in pulling query results made in access to use them in excel.
So far i have managed to create my database in access, populate it with data imported from excel and create the queries i need to use in excel. I have also managed to get the queries data in excel using MS Query (from "From other sources" menu because i would to query the query with parameters) and it is all peachy. It fails when i upload the access database on my work network. For some reason i can access the tables but as soon as i try to load my access query in MS query, it will just freeze to death.
I tried letting it run 20 minutes to no avail. I was wondering if anyone ever had that kind of issue. i tried several things for example i can access queries from other online database, the difference is that database is less heavy (the failing one is 100 mb) but considering i m a beginner i am not sure what else to do.
Thank you in advance
edit : i left it running and apparently it works, it's just that it takes a gazillion years : it is a sum query that runs on a 900k rows table
SELECT main.yearData, main.period, main.week, main.articleId, listArticles.brand, listArticles.description, groupToType.type, listArticles.model, listArticles.color, Sum(main.sales) AS totalSold, Sum(main.stock) AS totalStocks
FROM groupToType INNER JOIN (listArticles INNER JOIN main ON listArticles.articleId = main.articleId) ON groupToType.productGroup = listArticles.productGroup
GROUP BY main.yearData, main.period, main.week, main.articleId, listArticles.brand, listArticles.description, groupToType.type, listArticles.model, listArticles.color;
Is there anything i can do to make it run faster? i cannot wait 15 minutes every time to get the update info.7
Thank you again !
We have an SSRS report that has been running perfectly at multiple sites for over a year. It calls a MySQL stored procedure and displays the results in a table. For one particular customer who just migrated to a new server, this report now only shows one row of the results. It's a row that's early in the results but not necessarily the first row (not sure that has any significance). Below are steps I have taken so far to troubleshoot.
I've confirmed the procedure should return hundreds of rows by capturing the SQL via the slow query log, and running it directly on MySQL. So I've ruled out the data, the procedure, and the connection to MySQL.
This report does have grouping which I thought may be an issue, so I created a new report that calls the same procedure without any grouping and I get the same results.
As far as we know all other customers are using SQL Server 2008 R2, or 2016. This customer is using 2014. We have confirmed this customer does have all the latest SQL Server updates.
We have many other reports built in a similar way that work for this customer
We tried replacing the report RDL with another copy thinking it was perhaps corrupt
There has been one thing I've found to get all rows to show up. If I hard-code all parameters in the dataset, all rows will show up in the table. If any parameters are passed in (it doesn't matter which ones, or how many), only one row of the results shows up.
Dataset text examples
Displays one row
Call sp_report(?,?)
Displays multiple rows
Call sp_report('A','B')
These examples both return the same number of rows from MySQL according to the slow query log, but SSRS displays a different number of rows.
Any ideas would be much appreciated. I've been researching online and conducting many tests to try and figure this one out.
Update 4/16/2019
It's been 4 months and we still have not found a resolution for this. Now some other customers are starting to report this same issues. It still works for most customers and most reports, but there are a few cases where this occurs.
I have a Java Application that uses the JDBC:ODBC bridge for a connection with DBF Files linked to a Microsoft Access Database (thus, I'm using the driver for a connection to a Microsoft Access Database)
There is a table named SALFAC, that contains the following fields: NRO_FAC, COD_ITE, CAN_ITE, PRC_ITE and DSC_ITE among other columns. When I perform the following query: SELECT NRO_FAC, COD_ITE, CAN_ITE, PRC_ITE, DSC_ITE FROM SALFAC, without a WHERE clause it works fine. But when I execute the following: SELECT NRO_FAC, COD_ITE, CAN_ITE, PRC_ITE and DSC_ITE WHERE NRO_FAC=151407, my program throws a SQLException with the message The search key was not found in any record.
The NRO_FAC column is an integer type column, so using quotes results in a syntax error.
I compacted and repaired the entire database with no avail. Also, I tested the query directly on Microsoft Access 2010 and it gave me the same error. Yesterday I tested with another JDBC:ODBC bridge to the DBF files directly and also gave me the same error with the same query.
There is no blank spaces on the tables names and the columns names.
¿Is there any additional step to do in order to make queries like these work? I need execute the query with the WHERE clause. Also, for each DBF file is a NTX file. Must I do something with these files as well?
Thanks in advance
EDIT: I found something yesterday that might help. I changed the way I search the rows by inserting the entire DBF table content in an MS-Access temporary table, row by row, and then execute the query in the temprary table. It inserted the first 9 rows correctly, but the 10th row was next to a row that is marked as deleted and then the query crashed. Does the "marked-as-deleted" rows affect a query in MS-Access and/or dBase? If it does, is it possible ignore the "marked-as-deleted" rows using the JDBC:ODBC bridge? Also, must I install the Clipper commands (like DBU or PACK) in the server (it doesn't have them)?
We have a split MS Access database. The front end was distributed among us. And some users are able to run queries and edit query results without a hitch. But a few others are not able to edit the query results. The query runs fine for them and they are able to see the results in MS Access. But editing any field is not possible.
Could anyone advise me on how this can have happened. I have primary keys on all the tables on which the queries are based. And there are no joins in my queries. Each query runs on a single table.
Thank you in advance for your time and help.
With regards,
Manus
I got the answer. The back end database was on a network drive where some of the users had write access but not all. Silly of me not to look there first. So basically the users who couldn't edit were the ones with no write access on the shared drive in which the back end of the database was kept.