[MS SQL Server] Rename Server |
- Rename Server
- Restoring ReportServer Database
- Impact of creating a non clustered index
- MDF file too large. PRIMARY FILE GROUP FULL error
- Ideal Log File Size Set up in Sql 2008
Posted: 20 Aug 2013 04:52 AM PDT Hello EveryoneI am working with a company that needs, or wants to rename one of the SQL boxes to a name of an existing SQL box. The plan is to remove the original box from the network. Rename the other box to the name of the original server. My question is this: What impact will this have one the current SQL Instance that is on that new box? Will SQL Server Service even start?Has anyone tried this? Or had to perform this task? I do not have a couple servers on hand to test this, or I would.Thanks in advance for all your assistance, suggestions and comments.Andrew SQLDBA |
Restoring ReportServer Database Posted: 22 Apr 2011 12:47 AM PDT I'm setting up and testing a new SQL Server 2008 R2. I'm testing backup/restore of the ReportServer database using Management Studio.For an attempted restore I have the "Overwrite the existing database (with replace)" and "Leave the database ready to use by rolling back uncommitted transactions" options selected.I get this error message: "Restore failed for server: Exclusive access could not be obtained because the database is in use." I'm attempting to restore from full and differential backups. No transaction log backups.Can someone tell me the proper way to restore the ReportServer database? |
Impact of creating a non clustered index Posted: 20 Aug 2013 12:37 AM PDT Hi Experts,Please let know the impact of creating a non-clustered index on a table having 10million records and columns included in index are of int datatype.Thanks in Advance |
MDF file too large. PRIMARY FILE GROUP FULL error Posted: 19 Aug 2013 04:10 PM PDT I run SQL Server 2008 Express R2 on my local machine with Windows 7 Home Premium. I use the db to run a dotnetnuke 7 website. Everything went on fine until I got a "Cannot allocate space to object 'x'....PRIMARY FILE GROUP IS FULL" error message one day. I have cleared the logs from the application but the error persisted. I checked the database and found the mdf file has grown to over 10GB is size while the ldf file was around 175MB. The details of database are as follows:SQL Server 2008 Express R2Recovery Mode: Simplemdf file size: 10.23 GBInitial size: 10.23 GB (it shows the same)Space Remaining: 0.0 GBData File autogrowth settings: by 10MB, Unrestricted Growthldf file size: 173 MBLog File autogrowth settings: by 10% Restricted GrowthAlso when I try to shrink the file from the management studio-tasks it says cannot find such file. However the file is very well there in the path mentioned.Error DetailsFile Error Index #: 0Source: .Net SqlClient Data ProviderClass: 17Number: 1105Procedure: AddEventLogMessage: System.Data.SqlClient.SqlException (0x80131904): Could not allocate space for object 'dbo.EventLog'.'PK_EventLogMaster' in database 'hescom_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at PetaPoco.Database.Execute(String sql, Object[] args) at DotNetNuke.Data.PetaPoco.PetaPocoHelper.ExecuteNonQuery(String connectionString, CommandType type, String sql, Object[] args) at DotNetNuke.Data.SqlDataProvider.ExecuteNonQuery(String procedureName, Object[] commandParameters) at DotNetNuke.Data.DataProvider.AddLog(String logGUID, String logTypeKey, Int32 logUserID, String logUserName, Int32 logPortalID, String logPortalName, DateTime logCreateDate, String logServerName, String logProperties, Int32 logConfigID) at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.WriteLog(LogQueueItem logQueueItem)I am new to DB management and any help is appreciated. Thank You. |
Ideal Log File Size Set up in Sql 2008 Posted: 19 Aug 2013 05:59 AM PDT I would like to know what will be the ideal setting for Log file set up?I have Data File, Log File and Temp DB on seperate Disk drive.I have set up the Data File Initial Size: 100 GB - Growth - 5 GB as total Daat File Drive has 1 TB Capacity.I am little confused for Log file as We have Replication Subscription will be running on that DB and it will total size of the DB is 300 GB Plus.Replication will run frequently as well as couple batch job running.If I set up Log File: 50 GB - Growth - 1 GB as my total Log file drive is configured - 100 GB.Thanks and appreciate your response! |
You are subscribed to email updates from SQLServerCentral / SQL Server 2008 / SQL Server 2008 Administration To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google Inc., 20 West Kinzie, Chicago IL USA 60610 |
No comments:
Post a Comment