This How To shows you how to connect to SQL Server 2000 using a Windows service account from an ASP.NET version 2.0 application. You should use Windows authentication instead of SQL authentication whenever possible because you avoid storing credentials in connection strings and you avoid passing passwords over the network to your database server. You should consider encrypting your connection string to protect server connection details, such as the database server and name. By default, ASP.NET does not impersonate the caller to the database. On Windows Server 2003, you can use the network service account, which has network credentials (machine$), or you can configure an application pool identity. If you configure impersonation to use the original caller, you need to evaluate the scalability of per-user connection pools.
View SQL Link
Monday, May 14, 2007
How to Migrate from Access to SQL Server 2000
Microsoft Access developers generally consider a move to Microsoft SQL Server for performance, security, and stability reasons. This process is known as upsizing, and developers will find a number of key differences while migrating from Access to SQL Server.
SQL Server and Access are similar but have some major differences. They vary in the way that data is stored and indexed, the data types available, and storage capabilities. Microsoft provides the Microsoft Upsizing Wizard to assist in the migration process. It analyzes your Access database and converts your data and database structure into SQL Server format.
The Microsoft Upsizing Wizard effectively and accurately converts most of your Access database and database objects into SQL Server. However, some features in Access are not supported by SQL Server and vice versa, so it is important that you manually analyze and rectify any potential issues that may arise before, during, and after the migration process. It is also crucial that after conversion, the resulting database manually be inspected to ensure all tables, data, and relationships were correctly migrated.
This paper details:
• What the Upsizing Wizard does
• Preparing your Access database for migration
• Running the Upsizing Wizard
• What to do after upsizing your database
This paper does not cover reasons to upgrade to SQL Server from Access. More information about this can be found in the Microsoft white paper, "What's New and Different When Moving Your Back End from Access to SQL Server 2000."
View SQL Link
SQL Server and Access are similar but have some major differences. They vary in the way that data is stored and indexed, the data types available, and storage capabilities. Microsoft provides the Microsoft Upsizing Wizard to assist in the migration process. It analyzes your Access database and converts your data and database structure into SQL Server format.
The Microsoft Upsizing Wizard effectively and accurately converts most of your Access database and database objects into SQL Server. However, some features in Access are not supported by SQL Server and vice versa, so it is important that you manually analyze and rectify any potential issues that may arise before, during, and after the migration process. It is also crucial that after conversion, the resulting database manually be inspected to ensure all tables, data, and relationships were correctly migrated.
This paper details:
• What the Upsizing Wizard does
• Preparing your Access database for migration
• Running the Upsizing Wizard
• What to do after upsizing your database
This paper does not cover reasons to upgrade to SQL Server from Access. More information about this can be found in the Microsoft white paper, "What's New and Different When Moving Your Back End from Access to SQL Server 2000."
View SQL Link
How to obtain the latest SQL Server 2000 service pack
How to obtain the latest SQL Server 2000 service pack
SUMMARY
Microsoft distributes bug fixes in service packs. Service packs keep a product current. Service packs include updates and may include system administration tools, drivers, and additional components, which are conveniently bundled for easy downloading. Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, as well as any new fixes. You do not need to install a previous service pack before you install the latest one. For example, you do not need to install SQL Server 2000 Service Pack 1 (SP1) before you install SQL Server 2000 Service Pack 2 (SP2).
View SQL Link
SUMMARY
Microsoft distributes bug fixes in service packs. Service packs keep a product current. Service packs include updates and may include system administration tools, drivers, and additional components, which are conveniently bundled for easy downloading. Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, as well as any new fixes. You do not need to install a previous service pack before you install the latest one. For example, you do not need to install SQL Server 2000 Service Pack 1 (SP1) before you install SQL Server 2000 Service Pack 2 (SP2).
View SQL Link
Subscribe to:
Posts (Atom)