Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I work extensively with MySQL and have no experience with SQL Server. But I have an upcoming project where the existing site's database is on SQL Server. I will be needing to make periodic glances at the existing database, to make SQL dumps most likely so I can write a migration script to the new site database in MySQL. The client will be regularly updating this existing database so just asking for a one-time dump will not help.
Ideally I am looking for a web-based (or desktop based) tool which will allow me to log in to the SQL Server database (I have remote access) and allow me to make a dump or perhaps browse the database structure. Something similar to phpMyAdmin would be nice.
Update: I should clarify that web-based tools which are ASP based are not ideal. As much as I'd like to learn more about ASP, I do not have the time to set up another environment just to run the tool. Something hosted by a 3rd party would do the trick.
Several options are available (probably quite a few more, too):
SQL Web Data Administrator
SQL Server Web Tools
Article on web based admin tools
CiberSQL Web Admin
myLittleAdmin (commercial)
SqlWebArchitect
MSSQL Web Admin (broken link)
DBHawk (commercial)
You can also connect via ODBC to your remote MSSQL server then use MSAccess or OpenOffice to connect, browse or backup.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
Is there a site with details on how to setup a web .net app hosted on IIS requiring access to a db on a remote server? I can do this when both IIS and SQL Server are on the same box, using AppPool user...but don't know how to do this when the SQL server is remote. Our setup:
AD, both SQL Server and IIS servers are in same domain,IIS 7.8 and 8,SQL 2008 and 2012,Databases to be accessed by >1 IIS server. IIS is anonymous access
Is the most secure method to contune to use an app pool user on IIS, and to create a user on SQL with domainname\machinename$
Would I be right in thinking that this would work as the app pool user uses machinename$ Thus both IIS and SQL are using machinename$?
There are really 2 methods to do this:
1) Use SQL server authentication. Create a SQL user and use a connection string in the following format for SQL 2012:
Server=myServerAddress;Database=myDataBase;User Id=myUsername;
Password=myPassword;
2) Use mixed mode authentication and authenticate as a Windows user. Your connection string would look like this:
Server=myServerAddress;Database=myDataBase;Trusted_Connection=True;
You'd first go onto the web servers and create a Windows user. Remove it from the domain users group.
Then you'd go into SQL, add the user you're trying to connect with to the list of users, then grant read/write to the database you're trying to access.
If you go with this method, you'd set your app pool to run as the user you created and then add that user to the IIS_WPG group if you're running Windows 2003 or to the IIS_IUSRS group if you're running Windows 2008 or later.
Either one of these methods are perfectly acceptable. If you're running the webservers in the DMZ (not in your Windows domain), you'll want to go with option 1. If the webservers are in the domain, some would argue that option 2 is marginally safer because you're not storing the password in plain text, but you could still do option 1 if you felt like it.
Also, here's a pretty good site with a list of formats of connection strings for various versions of Windows/.NET/SQL:
https://www.connectionstrings.com/sql-server-2012/
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I have a system that runs on MSAcess and the client want to upgrade this to SQL Server. What version do I need to have on my development machine? If the client has SQL 2010 Enterprise will it be compatible with SQL Express on my development machine? What are the pitfalls of having these two different versions? Will I be able to backup my Express version and restore it to their 2010 Enterprise version?
All help will be greatly appreciated.
Regards
Mac
The best option is a Developer Edition. It has feature parity with Enterpise Edition but, as is only licensed for Developer work and not for production, it costs around $50.
Express Edition is also a feasible choice, as is free, but you'll miss some of the more advanced features and if your client(s) ask for these features you won't be able to test. Examples of useful features you'll miss are SQL Server Agent, Reporting Services, SSIS or Database Mail.
Will I be able to backup my Express version and restore it to their SQL Server 2012 Enterprise Edition?
Yes, as long as you make sure your version is at most the client deployed version and not any newer. You also need to ensure all your application is contained in the database (no dependency on logins, agent jobs etc), which is tricky. But you should absolutely do not do this. Your deliverable cannot be a database binary (mdf/ldf or backup), but it must be a script to deploy the database. If you fail to do this, your will have a big problem after one week when your client will ask for an update. Threat the database as code. See Version Control and your Database. Read about Rails Migrations for a good approach to this problem.
If you develop your application with an Express edition you should not have any problems if the user has a Enterprise edition running.
You can see the feature comparison sheet following this link: Features Supported by the Editions of SQL Server 2008 R2.
P.S. There is no SQL Server 2010. I think you mean SQL Server 2008 R2, thus the link provided links to that content.
If you upgrade your Access Database to a SQL Server Database you might have problems if you use Multiple Values in Access. For further possible incompatibilities follow this link.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am very new to TFS and SharePoint so I hope I can explain myself as best as possible.
We currently run a single server farm that runs on Windows 2007 Standard, SQL 2008, TFS 2010 and SharePoint 3.0. I have been given the fun task of upgrading this to TFS 2012 and SharePoint 2010!
Now I have been following the steps that Microsoft provide but I am still hitting problems along the way and need to know the best possible approach!
I have built a new server with all TFS & SharePoint requirements. Windows 2008 R2, SQL 2008 R2. I have also installed TFS and SharePoint 2010. Before I configure anything I then used TFS backup and restore tools provided with the new installation to back up the existing Database on the old server and restored the databases onto the new server running SQL 2008 R2.
Before backing up the databases I made sure I have a backup of the report server encryption key. When trying to restore this I have the following problem?
Microsoft.ReportingServices.WmiProvider.WMIProviderException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable)
Have I missed any steps for the upgrade?
Also when performing this upgrade, is there any chance of this interrupting our current TFS & SharePoint production server?
It sounds like you selected "Install but do not configure" when installing Reporting Services. For TFS 2010+ you need to have it configured as the TFS install will not do that for you like it used to in 2005/2008.
I have a blog post that includes how to configure RS: http://nakedalm.com/integrate-reporting-and-analyses-services-with-team-foundation-server-2013/
Although this is for 2013 it applies equally to 2012.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I have a database on my home PC. It is on Microsoft SQL Server 2012. I would like to access this data at work. There are 2 options that I am considering and would like to know how to achieve either.
Connect to the DB (home) via Visual Studio (work) online. How to do this?
Turn my home computer into a server. How to do this?
My PC is new and it is on the house wifi network. It is running Windows Server 2012.
If there are better suggestions I am willing to consider. This is for personal use- one user with roughly 50-100 mb data transfer daily to server.
As far as I know, you can connect to Your database from anywhere you want. But for achieving this You need to perform the following actions:
You need to check that Your SQL Server is configured to use both SQL
and Windows authentication (check link
http://technet.microsoft.com/en-us/library/ms188670.aspx).
You need to add a SQL login with needed permissions to Your database(s). Script can be achieved from here. But this operation can also be performed in UI on Your home computer.
You need to check that the port which Your SQL server listening on
is opened in your firewall (list of ports per protocols and Firewall
configuration described here:
http://technet.microsoft.com/en-us/library/ms144228.aspx)
You must have a static IP address on Your home computer. Otherwise the connection can be problematic. The "static" IP can be achieved using dynamic DNS. One of the possible solutions is described here
If all of the above were successfully configured, then you simply can connect to your SQL server by IP address with supplying needed credentials (user name created in the (2), password, target database).
Hope that this was helpful.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
As the title suggests, can Sharepoint 2010 be installed and successfully run on Azure cloud?
I am aware that Azure used to be stateless and as such could not support Sharepoint, but recent articles and posts seem to suggest that Mirosoft have resolved this.
http://www.theregister.co.uk/2012/06/27/microsoft_windows_azure_cloud_epiphany/
I have checked the Azure website and Sharepoint is mentioned but not specifically 2010 and I want to be sure it's a supported environment with no catches or unforeseen problems.
With the Spring 2012 release (which you read about with your link above), there are now Virtual Machines which are persisted to disks in Windows Azure blobs. SharePoint 2010 is one of the applications that's been specifically tested in this environment.
See this support page, where SharePoint 2010 (and other software) is explicitly called out.
You might find this TechNet article on creating a VM instance in Azure for a SharePoint farm helpful.