Created a new database called Test, when I try to connect to the SQL Server database via Excel I can't see the Test database which was created, I can only see master, msdb, tempdb.
I'm running SQL Server 2008 R2 Express.
I am new to Server Management, requesting some help so I can consume the data in an Excel sheet.
Got it fixed.
MS SQL was installed on a differnet domain and had windows authenticaion
When accessing from excel there was no option to choose windows authentication using a different domain.
Solution - Created a MS SQL User ID and gave access to the required database
Related
I have been tasked with building an application for a Windows laptop that engineers can take out into the field where there is no internet access. Then, they will add data through a form and once they get back and have internet access, they can then hit a "Sync" button and send the data they collected to an external SQL Server database.
The database is SQL Server 2016 and the application is going to be a C# .NET desktop application. My question is what options are available for the database when there is no internet access? I don't really want to do Excel or Access. I really like SQL Server Compact but it seems dated. Is SQL Server Compact still relevant with the latest .NET Framework or is there something newer that everyone uses?
You could try creating a ssis package that syncs data between the offline database and live database.
The ssis package can be executed either as a sql server job that runs at intervals
or
from a stored procedure . Please find the below link on how to execute a package from stored procedure.
https://msdn.microsoft.com/en-us/library/jj820152.aspx
The stored procedure can then be called from inside the application.
As the title says, I used to have SQL Express 2008 on my machine. After creating a new Web application, Visual Studio would automatically create the aspnetdb.mdf database and add a connection string to the Web.config file.
Since installing the full version I've found, to my surprise, that it's not possible to reference a local .mdf database any more. Firstly, is that true?
With that in mind, I used aspnet_regsql.exe to create an aspnetdb.dbo database on my local server. I then used the 'Server Explorer', in VisualStudio, to attach that database to the 'Data Connections'.
The problem is, every time I create a new web application, it sticks a local SQLExpress connection string into the project template.
Is there something else I have to do to rectify this?
Thanks
I installed adventure works, and I followed the instructions on this page:
How to: Create Connections to SQL Server Databases
basically nothing appears in the drop down, in step 2.
I cant even attach the database without getting an error, nor drag it to the web form.
It tells me that the database cant be attached cause it is version 705, and the server supports version 655..
Also what is teh difference between attaching the database and connecting to it?
I went to the installation center of 2008, and clicked on show installation info..I got this:
Microsoft SQL Server 2008 Setup Discovery Report
Product Instance Instance ID Feature Language Edition Version Clustered
Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS Database Engine Services
1033 Express Edition 10.1.2531.0 No Sql Server
2008 SQLEXPRESS MSSQL10.SQLEXPRESS SQL Server Replication 1033 Express
Edition 10.1.2531.0 No
so I guess it is installed on my computer, but I cant access the application
You need the database to exist in an instance of SQL Server (or whatever RDBMS you so choose...but most likely, SQL Server). To do this you can do a few things: namely restore a *.bak database backup file of AdventureWorks, or you can attached the mdf and ldf files (database data and log files) to get your database online.
basically nothing appears in the drop down
Do you have an instance of SQL Server installed on your machine?
Also what is teh difference between attaching the database and connecting to it?
Attaching the database is using mdf and ldf files to get your database online ready for transactions. Connecting to the database is creating a connection between a client application and the aforementioned database. Two very different steps of the data access process.
Attaching to a database is necessary when the database file(s) are in a location other than the default location. You don't really "connect" to a specific database per se. You connect to a sql server instance which contains a list of databases on that instance (or referenced by the instance).
When I attempt to add a SQL Server database to a website project (via add new items), I get the following error:
"Connections to SQL Server database
files (.mdf) require SQL Server 2005
Express or SQL Server 2008 Express to
be installed and running on the local
computer. The current version can be
downloaded from..."
This is despite having installed SQL SErver Express 2008 - and seeing it running under services.
A number of other instances of SQL have been on the machine in the past although they have been uninstalled.
I have tried reinstalling SQL & VWD several times to no avail.
Check the "SQL Server Instance Name" which is setup in:
Tools --> Options --> Database Tools --> DataConnections
Verify that the instance name matches your SQL08 instance.
As I'm learning the ins and outs of ASP.NET user management, I've learned that the default in VS is for it to use a SQL Server Express .mdf file for the data it needs to save. This won't help me for when I deploy my site, as I'm running SQL Server 2008 R2 on my IIS 7.5 server. I know that I can run a command line tool to automatically create the db tables necessary for user management, and will do that on my development machine, but how do I tell my existing, in development code in VS to ignore the existing Express .mdf file and look at the newly created db tables?
Simply update your Web.Config to set up the role provider and the database connection string:
http://weblogs.asp.net/scottgu/archive/2006/11/20/common-gotcha-don-t-forget-to-clear-when-adding-providers.aspx
http://www.codersbarn.com/post/2008/02/24/ASPNET-20-Guest-Book-Admin-Part-II.aspx
Also, Scott Mitchell's Membership and Roles tutorial series is the most comprehensive I've seen:
http://weblogs.asp.net/scottgu/archive/2006/05/07/ASP.NET-2.0-Membership-and-Roles-Tutorial-Series.aspx