SQL Server
Change page: < 1 2 3 4 5 6 7 8 9 10 11 >  |  Displaying page 10 of 11, items 271 to 300 of 326.
Mapping Local Logins to Logins on Linked Servers
For a user to gain access to a linked server, the linked server must validate the user for security reasons. The requesting server (that is, the local server) provides a login name and password to the linked server on behalf of the local server user
Obtaining General Information About Linked Servers
You can use both SQL Server Management Studio and the system stored procedures to gather information about linked servers and the referenced data sources.
Executing a Stored Procedure via a Linked Server
Executing a stored procedure is possible via a linked server. The server hosting the client connection accepts the client’s request and sends it to the linked server.
Setting Up Linked Servers Using SQL Server Management Studio
Although you can set up linked servers and login mappings by directly executing system stored procedures, you can also set them up easily through SQL Server Management Studio.
Encryption basics for SQL Server : Cryptographic Keys
The main character on the cryptographic stage is the key. A key contains the algorithm, the sequences of instructions which is used in the various cryptographic functions that SQL Server provides to encrypt and decrypt data.
Encryption basics for SQL Server : Key Maintenance
Cryptographic keys and passwords that protect keys are not a "set-it-and-forgetit" feature of securing sensitive data; they require periodic maintenance to ensure that the items that are protected remain at their highest level of security.
Encryption basics for SQL Server : Key Algorithms
Keys use a set of instructions that dictate how their cryptographic functions are to be performed. These instructions are called algorithms. There are several algorithms available in SQL Server and selecting the optimal algorithm can be a daunting task, with the high complexity of the mathematical equations that define these algorithms simply adding to the challenge
SQL Server 2005 : Performing Database Backups
Backups are an important part of any maintenance strategy. In a SQL Server 2005 environment, you can perform backups through the SQL Server Management Studio interface, by using T-SQL code, by using a customized application, or via third-party tools.
SQL Server 2005 : Restoring Data from a Backup
When disasters occur and you need to get the data back to a known state, you need to perform a restore operation. At other times, you might want to restore data, such as when preparing for log shipping or copying data from one server to another. You can also use the RESTORE command to validate backups or read the catalog information from an existing media set.
SQL Server 2005 : Using Database Snapshots
Database snapshots, which are new in SQL Server 2005, are available only in the Enterprise Edition. All recovery models previously discussed support the use of database snapshots. A database snapshot is a read-only, static view of a database captured at a specific time
SQL Server 2005 : Automating Maintenance with Job Scheduling
Many of the maintenance features discussed so far in this chapter are important, but they can be time-consuming. However, that doesn’t necessarily have to be the case. Essentially any task that can be performed from SQL Server Management Studio or through the use of a T-SQL query can be automated through the creation of a job or a schedule.
Other SQL Server XML Support
SQL Server 2005 has many features that utilize XML capabilities either directly or indirectly.
SQL Server 2005 : Managing XML Data (part 2) - The xml Data Type and Methods
The xml data type lets you store XML documents in a field within an SQL Server database or lets you store a variable within a procedure. By using the xml data type, you can store a complete document in a singular column.
SQL Server 2005 : Managing XML Data (part 1)
In general, XML is a data storage format that can be used to define and store data. An XML document is a data storage medium that lays out the data into elements and attributes in much the same way that a database has rows and columns
SQL Server : Removing Unwanted Data
Over time, data becomes obsolete and needs to be removed. You remove data by using the DELETE statement. It is extremely important to provide a condition when performing data deletions because it is easy to remove all data if you do not exercise caution.
SQL Server : Changing What Is Already Stored
You alter data through the use of UPDATE. Just as with the input of data, any alterations made to the data are subject to the rules and constraints defined in the table schema. Any data modifications made that do not meet these defined standards result in errors that the front-end application may have to trap and control.
Using System Tables and Views
SQL Server tracks information and maintains data about every object in the system. This information is maintained in system tables that can be queried like any other tables
SQL Server 2005 : Data Querying Using Full-Text Indexes
Full-text indexes are special indexes that efficiently track the words you’re looking for in a table. They help in enabling special searching functions that differ from regular indexes.
SQL Dependency Reporting
Another issue that you face when administering SQL Server instances across an organization is determining object dependencies between servers and databases. If you have to make changes to objects in a database, it is hard to establish a list of items that may be affected (especially if the referencing objects are on another server)
The Overall Disaster Recovery Process
In general, a handful of things need to be put together (that is, defined and executed upon) as the basis for an overall disaster recovery process or plan.
Microsoft SQL Server Options for Disaster Recovery
You have seen the fundamental DR patterns you will be targeting and also recognize how to identify the highest priority applications and their tightly coupled components for DR
How to Approach Disaster Recovery
Often, disaster recovery specialists refer to a seven-tier disaster recovery paradigm. These tiers start at the bottom of the disaster recovery food chain—Tier 0 (no offsite data—possibly no recovery) and progress up to the highest level of disaster recovery possible—Tier 7 (zero to near-zero data loss with highly automated recovery).
SQL Server 2008 : Database Mirroring
The technique of database mirroring can be summed up very simply: It's the practice of keeping two separate copies of your database in synchronization with each other so that if you lose one copy, you can continue work with the other.
Creating and Using a SQL Azure Database
Let’s start by creating a SQL Azure database and playing with it a bit. SQL Azure’s signup process and development experience are slightly different from the rest of the Windows Azure storage services.
SQL Server 2008 : Failover Clustering
Failover clustering is a technique that uses a cluster of SQL Server instances to protect against failure of the instance currently serving your users.
SQL Server 2008 Reporting Services : Management and Security
SSRS provides a set of useful tools for managing and securing all reporting objects. The following sections discuss tools and the overall security model in detail.
SQL Server 2008: Security and User Administration - Authentication Methods
The first level of security encountered when accessing SQL Server is known as authentication. The authentication process performs the validation needed to allow a user or client machine to connect to SQL Server. This connection can be granted via a Windows login or SQL Server login.
SQL Server 2008: Security and User Administration - Managing Principals (part 2) - Roles
Roles provide a consistent yet flexible model for security administration. Roles are similar to the groups used in administering networks. Permissions are applied to a role, and then members are added to the role. Any member of the role has all the permissions that the role has.
SQL Server 2008: Security and User Administration - Managing Principals (part 1) - Users
Every principal granted security to SQL Server must have an associated login. The login provides access to SQL Server and can be associated with principals scoped at the Windows and server levels. These logins can be associated with Windows accounts, Windows groups, or SQL Server logins.
SQL Server 2008: Security and User Administration - Managing Securables
Securables are the entities in SQL Server on which permissions can be granted. In other words, principals (for example, users or logins) obtain permission to securables.
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
- First look: Apple Watch

- 3 Tips for Maintaining Your Cell Phone Battery (part 1)

- 3 Tips for Maintaining Your Cell Phone Battery (part 2)
programming4us programming4us