I have an ASP.Net web application that runs off of Access databases. I want to convert the application to run off of SQL Server. Will this be a simple process to do? I am thinking that it only involves changing the queries that run on an Access format so they can run on an SQL Server.
Is it that simple or is there be more to it?
Migrate DB to SQL Server with MS SQL Server Migration Assistant for Access
Review migrated DB and verify that tables have been migrated and that column data types have been set properly.
Modify connection string in web.config so that it is now pointing to the SQL Server DB
Review your query code and modify as necessary. The T-SQL used in SQL Server will be different from the JET SQL used in Access. Do a search for Quick-Access-JET-SQL-to-T-SQL-Cheatsheet and you'll find a list of differences.
Microsoft SQL Server Migration Assistant for Access
SQL Server Connection Strings
Related
I would like to know after upsizing ms access database to sql server successfully with my user name in the domain and windows authentication and linking access tables to sql server tables,
for distribution this front-end to other users in the domain what i have to do? Is enough give a copy of the front-end to other users and defining their user names and permissions in the sql server? Or it needs some vba code in ms access for defining linked tables and ODBC connection?
Yes, if the ODBC driver you use is installed on users' machines - and, of course, Access is installed.
Table links don't change. If you didn't use Windows authentication, however, tables had to be relinked using each user's credentials.
I have an ASP.NET application on Server A and a SQL Server on Server B.
When running the appliction it calls a stored procedure. This procedure try to bulk insert from a file from a shared folder on Server A, but the following error occured:
Cannot bulk load because the file "\serverA_address\sharedFolder\test.txt" could not be opened. Operating system error code 5(Access is denied.).
The strange is that when I execute the bulk insert from the sql management studio directly, it runs without any exeptions.
Another observation: if I change the shared folder address to a local folder where the sql server runs (Server B) without shareing, no access denied error...
I tried to set bulkadmin permission to all the users, including the technical users: sql_serviceusr who runs the sql service, another technical user who runs the application and make the call to sql server and to the user who logged in to the application. All users are domain accounts and all servers using Kerberos authentication.
Server A: Windows Server 2008R2
Server B: Windows Server 2008R2, SQL Server 2008R2
Appreciate any help or guidance.
You are doing a double hop, so you need to enable Kerberos delegation.
You could create a connect account and use SQL authentication.
In my experience, getting our network folks to properly set up Kerberos is like pulling teeth. We had it working for one glorious week once and then it suddenly stopped working. It just wasn't worth the hassle after that.
This might not be the exact answer you're looking for, but could be an interim solution for you.
By your description of the error, I assume the problem is in sharing the folder.
When sharing a folder, you should give access to the user who will be accessing the folder from remote computer in two places in folder's properties: under the Share tab and under Security tab.
Did you give access in both of them?
I have VSTO application that needs to access a SQL server database but it cannot do it directly. I have thought of two ways to perform this task, but I don't know if those are the best ones :
Creating a "fake" aspx that will be accessed from the VSTO and that will call the SQL server database
Hosting a web service on my distant server. This web service will be accessed from the VSTO and will call the SQL server database
Your second option is the way to go. Create a WCF service, and have this access the SQL Server in a trusted environment. You can protect the service with Windows Authentication, or otherwise pass a user name/password or session key with every call.
how can two or more applications use single ASPState database.
I had implemented SQL server session management. I have some asp.net applications deployed on my IIS where i want to implement SQL server session management, so i have ASPState DB, i want to share this DB for all applications.
DB- data base
If you're using the default ASPState database created by the supplied SQL scripts that come with .NET, the database is already designed for shared usage. Just configure each application to point to the same database. The session state is isolated in the db by using the application ID from IIS (i.e. /W3SVC/2165464565), so there's no collision of data.
I am working on asp.net membership website. I created the membership provider automatically, and now its stored in sql express database within the solution. I want to move all the tables to sql database instead of sql express. Last night I attached the sql express database to the sql server management studio, and I was able to see all the objects. Then, I run my solution in visual studio, and I got error: LOGIN FAILED for the sql express database, and the solution wasn't running.
I have two questions.
1. Why is that happening?
2. If I create the same database in sql server with the same objects, and then point to the sql server database instead of sql express database, will I have problems with the membershop provider?
Thanks in advance.
It sounds like you've moved a database from one host (running SQL Server Express) to another host (running a non-Express SKU). Is this correct?
Ensure that your membership connection string is pointing to the new location of the membership (the non-Express SQL Server). Ensure the logins and users are setup properly in the new SQL Server instance, as expected.
Attaching a database to a new server does not automatically create the necessary logins.
run exec sp_change_users_login 'Report' from within SSMS on your database.
If it comes back with anything in the result set, you'll need to run exec sp_change_users_login 'Auto_Fix', '<username>'
where is the username from the first result set.