I am experiencing weird behavior when trying to call a stored procedure using subsonic from a website. I am getting "time out expired" error when I call the stored procedure using subsonic. If I execute the same stored procedure in sql server management studio, it runs instantly. I am not knowing what the problem is. I cannot step into the code because it is referenced as a dll. I am using version 2.1. Please let me know if you have any ideas.
Thanks,
sridhar.
It is my fault. I have a transaction open in the sql server management studio. Then I ran an update statement on a table. All the records affected by that update statement are locked because of transaction. it is working for some employees because those records are not locked. I ran the sp_who2 to determine the locked processes and figured out the problem.
Thanks,
sridhar.
Related
I have a stored procedure I've created for postgres. The app I'm developing has backend done in node and I've got to upload the stored procedure to our dev server. By upload I just mean to persist that stored procedure in the dev server by executing the CREATE PROCEDURE... .
How is this process usually done? I mean, I could just copy the code and paste it on our dev's pgadmin and that would work. But, creating a migration file for that would also work. Also, executing a CREATE OR REPLACE PROCEDURE raw query inside the code itself would also work.
How is the process of uploading a stored procedure on a postgres running server usually done?
There's no definite consensus on this. I've written a console task to do that in a PHP application to apply it, and with hindsight I think that was the wrong choice.
I quite often make other non-structural changes, such as updating or deleting existing records, in a migration, and that is the method I would be inclined to use now.
From time to time when I run some queries I get this error message :
An operation that uses the database driver could not be completed. If the driver is a Microsoft driver, make sure the driver file isn't damaged
I didn't found yet how to fix it with internet help.
this last website give a "solution" but I can't do the same.
"Well in my case it worked by giving the user access to the DB it is accessing."
I just have a worksheet who use others files from my company network, I don't use any database ...
I can't reinstall the driver or anything else, my company have a very strict politic about IT security.
May I have some help ?
I had the same issue when I try to connect Analysis service in Azure. The error message is misguiding. In actual, you are missing few client drivers that are needed to connect to Azure Analysis services. Install all the missing drivers (OLEDB, AMO and ADOMD) from https://learn.microsoft.com/en-us/analysis-services/client-libraries?view=asallproducts-allversions#known-issues and you should be good to go.
I think OLEDB installation should suffice the need but I did all three to avoid future encounters related to other admin stuff. Check if OLEDB updated # C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\140 by comparing msolap.dll version. Latest version as I write this is 15.1.108.23
Tip: 1) Try connecting to Analysis Service from Excel by following the steps - Data Menu --> Get Data --> From Database --> From Analysis Services. Follow the prompts by filling appropriate info. Bingo! You are in!
2) Wait for a while if still you can't connect after installing all drivers. I don't know the actual reason why but was able to connect next day.
Please mark this as an answer if it helps to solve your problem.
Good Luck!
Update - 1/5/2021
Today I face same ugly error again which made me to rethink what else could be gone wrong in the system. Later realized that I had restarted the machine and that removed the temp connection file referred by Excel file. Following the steps to reconnect under the Tip section in above instructions let me successfully in.
I've been working with Powerapps for about 3 to 4 months now, and this particular app I've created connects to 3 tables in an Azure SQL Server Database. It's been working great until today. This morning I logged in to edit a feature on the app and my galleries were empty with an error message saying: "Bad Data source Inner exception, Not a valid data Source".
My first thought was, something is off on the database, some planned work possibly during the night, but that's not the case, and the DB is working perfectly as I also use it in PowerBI.
I googled for the error and found several people with a similar issue, and most of them reported that deleting the Data Source connections from power apps and adding them again would fix the issue, as well as deleting and creating the Galleries again. I've performed both actions, and the same error returns. I tried creating a fresh new canvas app, with a gallery and a brand new connection to the Azure Sql DB and still got the same error. I've also tried to restore one of the oldest versions of the app, and I still got the same error. This to me all indicates there's a problem with the DB, but...when I publish the APP, and run the app after publishing, It works perfectly, and I have full usability of the app, which means the connection to the DB is actually working.
It feels like a bug to me. I'll share the screenshot of the error:
Error Message
I'm worried I will lose all my work, so if someone could help me, that would be great.
Finally, I got the solution for this issue. This are the steps I followed to solve the issue.
Remove all the Database connectors from your app.
Go to File -> Settings -> Advanced Settings -> Disable enhanced Microsoft SQL Server Connector.
Add all your Database connectors back again.
A couple of days ago I set up Azure Database Sync in order to keep the backup DB and the primary one synced. But after doing that, the database used as a hub is no longer visible on SSMS Object Explorer. If I stop the DB Sync, it shows up normally. I have admin rights on the database. The problem is that if I have to check anything on the database, now I cannot. Has anyone any advice about this issue?
UPDATE:
For everyone facing the same issue, one workaround is to open the database via Visual Studio. in VS, the database is listed as it should be
Applying getting the latest SSMS will most likely solve this problem.
msdn.microsoft.com/en-us/library/mt238290.aspx
After installing a custom CLR object Sql Server Developer Tools (SSDT) VS2012 will not allow an update. The error is "Source schema drift detected. Press Compare to refresh. After refresh same thing happens.
Tried
In settings, I set the object to just Stored Procedures.
Settings ->General -> Block on possible data loss -> tried both on and off.
This sort of loop can also be caused by a referenced SSDT project failing to build. The referenced project may be missing, unloaded, or have an error which prevents the compare from completing.
This is not an answer but a clue to deal with this problem.
I was to update a colum from varchar[200] to varchar[MAX] and got this problem as well. So I logged in the server and tried to update the database manually via SQL Management Studio which was installed there, and I got this error:
"Saving changes is not permitted. The changes you have made require the folloing tables to be drpped and re-created. You have either made changes to a table that can't be re-created or enable the option Prevent saving changes that require the table to be re-created."
Seems that re-creating table is something so dangerous that "block/unblock on possible data lose" cannot handle. So I think only if we can walk around this LOCAL warning, could we update the database REMOTELY.
But, why [200] to [max] leads to re-creating table? It does not make any sense. I tried [200] to [1000], and it did not work as well. This might be the key to this problem.
And, if you do the same update in Server explorer in VS, instead of SQL Management Studio, it works. Again, why?
This can happen when a db user "changes".
The following rather scary forum page recounts issues where foreign hackers were trying to brute-force access to the "sa" db user, with each attempt changing the sa-user's date timestamp (which is seen as a schema drift):
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/5c22a7b4-7a82-4717-a118-2475bc62705b/schema-compareupdate-error-target-schema-drift-detected?forum=ssdt
Here is also mentioned that you can query the sa-user a few times, to see if this is happening to you:
SELECT * FROM sys.server_principals WHERE principal_id=1
I am currently experiencing the same issue (that the sa-user is being modified; I know nothing about hackers yet) and am yet to find a solution.
Edit - I turned on logging in Windows Firewall via properties > logging, and we setup a blocking rule on port 3071, which had a lot of unexplained traffic. Then the problem went away.
I tried running VS as an administrator, it worked.