I'm trying to compare the Azure SQL Managed instance to my local database project. But when I make a selection of the database "Ok" button is not getting enabled.
This used to work a month ago but all of a sudden it stopped working.
It's an issue with only one Azure SQL Managed Instance. We have one more Azure SQL Managed instance which is working alright(We can compare successfully).
And also it's just with Visual Studio, I have tried Visual Studio 2019 as well. We can compare alright in 'Azure Data Studio'.
Same issue with MI. Fixed by manually editing SchemaCompare.scmp file. Just add your source module section:
<SourceModelProvider>
<ConnectionBasedModelProvider>
<ConnectionString>Data Source=db.database.windows.net;Initial Catalog=aaa;Persist Security Info=False;User ID=xxx;Pooling=False;MultipleActiveResultSets=False;Connect Timeout=60;Encrypt=True;TrustServerCertificate=False;Authentication="Active Directory Interactive"</ConnectionString>
</ConnectionBasedModelProvider>
</SourceModelProvider>
Related
I'm using Visual Studios 2012 and SQL Server 2014. Here's my problem. If I deploy my SSAS solution to 'localhost' everything runs smoothly. When I try to deploy it one of our other servers I receive these errors. I’ve tried changing the accounts in ‘Impersonation Information’, but still get the same errors. I've also made sure I have all admin rights. It’s going on two days and I still cannot find the fix. Errors: enter image description here
"Class not registered" error indicates your data source (SQL) connection string is using a driver not installed. For example if your connection string uses a SQL2008 driver accidentally (with a Provider=SQLNCLI10.1 connection string) it will give this error when you try to process on the server.
Three options to fix it:
Fix the connection string in Visual Studio to use the version of driver that's on the server before you deploy.
Install the version of SQL Server Native Client you use on the server
Deploy without processing the cube, RDP to the server and open SSMS and connect to SSAS and fix the connection string then process.
Thank you for the help.
I had to create the SSAS project in BIDS 2008. Also, I had to delete the dimension created when the cube was created. I then created a new dimension using multiple columns as my unique key. Then, attached new dimension to the cube.
ASP.NET 5 project, Entity Framework 7. Using all the default stuff that comes with the ASP.NET 5 web template for creating the Identity Context. When I start up the app and first try to hit the context (register or log in), there is an error on Database.AsRelational().ApplyMigrations() that the database already exists. However, when I connect to the database matching the connection string in config.json, I do not see the database.
"ConnectionString": "Server=(localdb)\\mssqllocaldb;Database=aspnet-myAppDb;Trusted_Connection=True;MultipleActiveResultSets=true"
Connect to (localdb)\mssqllocaldb in SQL Server Management Studio, delete the database there. I'm not sure why this step is required or why the migrations fails, however.
There is an already accepted answer, but I prefer doing this from Visual Studio. This is caused by manually deleting the MDB file. For future reference, you should not delete the MDB files from Explorer, but instead use Visual Studio or SQL Server Management Studio to delete them.
In Visual Studio, hit Ctrl+\, Ctrl+S to bring up SQL Server Object Explorer. If your keybindings are different, look under the View Menu.
Expand the node for the type of localdb you are using, find your problem database, right click and delete. Problem fixed.
I am trying to migrate MOSS 2007 to sharepoint 2010 and I got the error while restoring the backup. The steps I followed are
I have the back up file and all solution pakcages from MOSS 2007.
I have a brand new server setup with sharepoint 2010 and Sql server 2008(64 bit) and windows server 2008 (64 bit).
3.I have created a new web application and new site collection.
4.Successfully Deployed the solution packages using powershell command.
5.trying to restore the backup and got the error
Restore-SPSite: THe site collection could not be restored, If this problem persists please make sure the content databases are available and have sufficient free space.
CAn anyone help me how to resolve this. I tried following some suggestions I got through google, but nothing worked for me.
Thanks
You can't directly restore the moss2007 backup to sharepoint 2010. You need to restore it back to SharePoint 2007 and then migrate it. If you have a database backup of the content database, then you could follow the steps given:
Take the backup of the content database from the SharePoint 2007
database server.
restore it to the database server of the 2010 environment.
Run the cmdlet Test-SPContentDatabase –Name -WebApplication using powershell to make sure that all the required dependencies are available on the 2010 server.
create a new web application on the 2010 server and add the content
database to it. upgrade the visual look of the web application by
doing to the site settings.
I hope this will help you out.
This is my first try of Visual Basic 2010 Express, though I have 10 yrs+ experience in VBA.
I'm running Windows XP SP2 on a desktop pc with following installed:
Visual Basic 2010 Express... just installed!
SQL Server 205 Express ... been running on pc for 12 months
I've created a new DB in SQL for my test application, but have not added any users or permissions to it as I'm using Windows authentication.
I've created a new Windows Forms Solution in VB2010EXP and tried adding a new Data Source for my new SQL DB, but it keeps giving error message about not having rights ot the db.
2 days of searching on the web has confirmed many others with similar issues, but no obvious solution. Eventually I find a few threads about permissions and moving the mdf into the root of the HDD, so try moving my mdf file up closer to the root of the Hard Drive
msf was in C:\Documents and Settings\_SharedData\Application_Data\MSSQL2005\Data\
now in C:\SQL2005\Data\
Now I can finally add a data source to my Db and start to use VS.
Problem is now occasionally when I am workng in VB and then go to the SQL Management Studio and try and view/change my DB, it gives an error and I cant access my DB. I then have to detach and re attach to my DB before I can work on it.
So my questions are:
Surely the location of my MDF file
should not be critical???
Do I need to add a user and
permission to my DB or should VB be
able to deal with this automatically
as I'm using windows authentication
Are then any known issues with
VB/VS causing errors in SQL
Managment Studio?
Thanks in advance
Grant
SQL Server runs on a different Windows Account to the one you use. You can check this by going to services (Run > Services.msc) and under SQL Server, go to properties and the Log On tab. I think by default 2005 uses the 'Network Service' system account. Now the reason you can't attach an MDF sat inside your documents folder is that account doesn't have access to your documents. You could give it permission, but you're much better off having the databases closer to the root as you have done.
Your connection to the database is driven by the connection strings you use. My personal preference is to create SQL Login accounts for my applications, and give them the least possible permissions they require. You could do the same using a Windows Account if you prefer.
I'm sure there are a couple. What is the error you are getting that prevents you accessing the Db? If we can see this error we may be able to help better.
Hope that helps.
I've created a "Database project" (.dbproj project file) in Visual Studio 2008, added a couple of tables there and selected "Build->Deploy". Visual Studio said it has successfully deployed my Database1.sql into (local)\SQLEXPRESS.
Now I'd like to see the database - be able to delete it or just see that it looks right - but I can't find where the database is and how to manipulate it without writing code. How can I get a hold on the newly created database?
You can use the SQL Server Management Studio stand alone application, or the Server Explorer in Visual Studio.
There are also a lot of tools from other vendors like Toad or SQuirreL...