Symptoms
When a database is in the full recovery model, and you try to back up the transaction log files with either a NO_LOG or TRUNCATE_ONLY option, the following message is logged in the Application Log of the Event Viewer:
Event Type: Error Event
Source: MSSQLSERVER
Event Category: 6
Event ID: 17055
User: <User name>
Computer: <Computer name>
Description:
18278 :
Database log truncated: Database: <Database name>.
Note The same message is also logged in the SQL Server 2000 error log.
If you use SQL Server 2005, the following message is logged in the Application event log:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 8309
Description:
BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log.For more information, see Help and Support Center at http://support.microsoft.com.
Resolution
This warning message may be logged because the NO_LOG and TRUNCATE_ONLY options of the BACKUP statement truncate the transaction log files, and you might need transaction logs for the full recovery of the database.
Symptoms
When you install SQL Server 2000 Service Pack 3 (SP3), a Microsoft Windows user account named SQLDebugger is created. This article discusses the SQLDebugger account, including when the account is created, the default permissions that are assigned to the account, and when the account is used.
Resolution
The SQLDebugger Windows user account is created when the SQL Debugger Registry2 DCOM server process (Sqldbreg2.exe) is registered. By default,SQL Server 2000 SP3 registers this process, and the SQLDebugger Windows user account is created.
SQL Query Analyzer includes T-SQL Debugger. By using T-SQL Debugger, you can control and monitor how stored procedures run. T-SQL Debugger uses the SQLDebugger Windows user account to connect to the database server.
Microsoft Visual Studio .NET applications use SQL Server Debugging to debug SQL Server stored procedures. The SQLDebugger Windows user accountis also created when you install Visual Studio .NET.
Note The SQLDebugger account is created by usinga strict random password policy for security purposes. If the password does not comply with the effective local password complexity policy, the SQLDebugger account is not created and the DCOM server is registered to run under the interactive user account. This prevents SQL Server Debugging from working correctly when you run Visual Studio .NET in the Terminal Services client session.
The SQLDebugger Windows user account has the following characteristics : It belongs to the built-in Windows Users group. It does not have local logon rights.
Note The Deny logon locally security setting is set for the SQLDebugger account.You can log on to the SQLDebugger account by using a batch-queue facility.
Note The Log on as a batch job security setting is set for the SQLDebugger account.By default, the User cannot change password and Password never expires options are set. System users do not have default permissions to use this Windows user account to explicitly connect to the computer running SQL Server.
Warning Microsoft recommends that the administrator of the computer where the database server is installed and the database administrator should not give any explicit permissions to this account. Explicit permissions to this account may lead to security vulnerabilities.
If you do not want to use SQL Server Debugging against the computer running SQL Server, you can delete the SQLDebugger Windows user account. For additional information about how to enable SQL Server Debugging, click the following article number to view the article in the Microsoft Knowledge Base:
318632?(http://support.microsoft.com/kb/318632/EN-US/) FIX: SQL Debugging May Fail Because of Strict Local Password Complexity Policy
blogging
|
account, dcom server process, Knowledge Base, logon rights, microsoft visual studio, Server, SQL, SQLDebugger, terminal services client, user, windows users group
Symptoms
This article describes how to change the Microsoft SQL Server 2005 service accounts by using the Microsoft Windows Management Instrumentation (WMI) Provider for Configuration Management. This article contains a script sample. You can use this script sample to change the SQL Server service accounts.
Resolution
Permissions on the accounts that are used by SQL Server 2005 services are managed by group membership. When you try to change the SQL Server service accounts by using the Windows Service Control Manager, you must manually remove the old accounts and then add the new accounts to the corresponding groups. Therefore, we recommend that you use SQL Server Configuration Manager to change the SQL Server service accounts.
SQL Server 2005 provides the WMIProvider for Configuration Management. You can use the WMI Provider for Configuration Management to manage changes to group membership and changes to service accounts. Specifically, you can use the WMI Provider for Configuration Management in a script file to simplify the operations. For example, you can repeatedly call a script file to automate changingthe SQL Server service accounts each month.
Facebook fan page for Star Wars
Building business on social network has become the need of the hour. If you want to reach your target audience and create a niche for your brand online, you should be promoting your line of clothing, products or anything over the web. And at present, Facebook, the networking giant, is the place where most businesses are advertising about their brand and products with through Facebook fan page.
A facebook page allows you to promote your business/products over the web. With a facebook fan page, facebook users are able to directly connect with the companies they love. Currently, all big names in the industry have a facebook fan page to interact with their customers.
This setting serves a dual purpose. Facebook news feed keeps the users abreast of the latest happenings and offers of the companies, while the companies get a word-of-mouth; there is also a definite spread of their online presence.
The latest news that is doing the rounds is regarding Lucasfilm Limited, a production company that was launched by George Lucas in 1971. This company is latest to join Facebook page bandwagon. The company is famous for delivering massive hits like Star Wars, Indiana Jones and sequels to these box-office blockbusters.
Lucasfilm has recently launched their official Facebook page dedicated to Star Wars saga. Rumors are that the company is thinking about re-releasing the Star Wars series in 3D. In its foremost post, Lucasfilm had invited its fans to look out for recent developments regarding Star Wars. The page will be updated every now and then for latest news, events and much more for its fans.
Just a few days back, the company disclosed the news about releasing the complete saga of Star Wars in a Blu-Ray box set. Lucasfilm said that they will be posting more info regarding this release on the facebook fan page.
The fan page already boasts of 4,009,639 fans. So if you are an avid fan of Star Wars movies, you can become a fan by simply logging into your facebook account and search for Star Wars.
Keep yourself updated with the latest buzz regarding your favorite Star Wars saga. And yes, if you have a business that can reap profit then follow the biggies of business and launch a Facebook fan pages.
blogging
|
box office blockbusters, company, D. In, facebook, fan, George Lucas, Indiana, networking giant, page, Ray, Star, star wars saga, star wars series, target audience