On our dev system, the trace flags 1204 and 1222 are on, deadlocks are detected and resolved, the reports appear nicely in the profiler, but they are not appearing in the system log. SQL 2008 not R2, 64 bit standard edition.
Also the system health event seems to have died in January, I'm just looking into that now, could it be related?
Thanks.
Josh
In a 2 node Availability Group with tcp and named pipe protocols enabled, how can you get named pipes to work ?
Say for example I have a Windows cluster called DEVL with 2 nodes DEVLA and DEVLB with an availability group listener called DEVLS.
All 4 have IP addresses(DEVL, DEVLA, DEVLB, DEVLS).
In a traditional cluster(before Availability Groups) we would specify the virtual node name when configuring the named pipe. The windows cluster would then determine which node was the active node(active/passive configuration).
Now, in a non-shared storage availability group we have 2 separate sql server instances and we connect to the listener name. The listener is configured with 2 tcp endpoints(default port 5022). It appears to not know anything about named pipe protocol as the listener is configured to use tcp.
If we setup a named pipe alias to use the windows cluster name, it will point to which ever node is the active node in the cluster. This might not be the primary replica pointed to by the listener. i.e. The cluster could be active on the DEVLB node and the listener points to the primary replica which is on the DEVLA node.
If we setup a named pipe alias to use the DEVLA or DEVLB node names, it of course points to just those physical nodes whether they are the primary replica or not.
If we setup the named pipe alias to utilize the availability group listener name(DEVLS), it just hangs and never connects. Both nodes have named pipe endpoints configured with public access and hadr_endpoint endpoints using tcp for the sql server service login.
The error we receive when we try to connect to the listener through named pipes is:
error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, error: 2)
Is there something we missed ? Do we need to setup named pipe endpoints somehow to 5022 ?
I have a big delete operation, then while deleting the server went on a restart.
When opening the server again, I got the database In Recovery mode.
What is the solution?
Greetings! I've installed and successfully configured our SQL 2012 AlwaysOn 2-node servers for our new "Intranet" that is coming out. I've gotten AlwaysOn working great, and our Front End servers for the Intranet will be using SharePoint 2013. The glitch is that SharePoint 2013 is configured to add databases automatically to our SQL Server 2012 back end, but NOT to AlwaysOn. In reading about this and in contacting Microsoft MSDN support, the default answer is "you must manually find, select, back-up and then add those new databases individually to get them into AlwaysOn."
But wait; that can be quite a task, constantly checking the SQL Back-end servers to see what databases were created, then having to add them into AlwaysOn, 7/24! I'm looking for a script or process that will check for new databases, back those new databases up in FULL mode, (for being added to AlwaysOn, of course) then add those databases to AlwaysOn, all automatically. Or have this run every...1-2 hours? (without user intervention)
What I've come up with so far is this script that actually identifies the newly-added databases, (not yet in AlwaysOn), and then backs them up to a shared location. My next task is to find those newly-added databases and through the various processes needed, get them added to AlwaysOn. This will involve some sort of looping action, I imagine. I'm not a T-SQL/scripting guru; is there any solution or script that I might access that would do this? (add databases to AlwaysOn automatically)?
Please advise, I'm sure I'm not the first person to have this issue. I have seen previous posts on various Internet Sites, and the solution is "sure, go ahead and just script that!". Thanks, but I need just a little more detail there.
Thanks again,
-Allen
DECLARE @name VARCHAR(50) -- database name
DECLARE @path VARCHAR(256) -- path for backup files
DECLARE @fileName VARCHAR(256) -- filename for backup
-- specify database backup directory
SET @path = '\\atel-web-be2\backups\'
DECLARE db_cursor CURSOR FOR
select name from sys.databases
where group_database_id is null and replica_id is null and name not in('master','model','msdb','tempdb')
OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @name
WHILE @@FETCH_STATUS = 0
BEGIN
SET @fileName = @path + @name + '.BAK'
BACKUP DATABASE @name TO DISK = @fileName
FETCH NEXT FROM db_cursor INTO @name
END
CLOSE db_cursor
DEALLOCATE db_cursor
We have a SQL server which has 24 GB RAM that runs slowly when doing a big SSIS package run (last about 4 hours). I see Page Life expectancy is very low , it goes down to 7 when the packages are running, when it is not running the server shows 25000 PLE. I think it is under memory pressure when the packages run. But the developer says the PLE could be a bit of false alarm where ETL concerned, They ran about 100 packages each night, most of thos 100 packages access different data set. So they think most of the packages don't reuse any cached data the previous pacakges users.
So why the PLE is so slow when the Packages run?
Thanks
SQLFriend
I have heard rumors that calling a stored procedure runs a little faster if you specify the schema, as in "exec dbo.mysp".
We have an app that is sending commands to SQL Server as RPCs, judging by the profiler. The textdata field *shows* as "exec mysp". Is there any speedup available by somehow specifying the schema as dbo? Exactly how is it likely that would be done in the app, in C#?
Thanks,
Josh
Had the case a few days ago I get an email about a job that failed. Although the name looked familiar, after taking a look at the server, I concluded it was not something I had worked on. What are some ways I can tell who created the job and when?
Hi,
We migrated our sql server instances that are mix of 2005, 2008, 2008 r2 (standard, enterprise) from physical to virtual. We have UCS in our data centre. In VM environment we are sharing CPU. Our licenses based on per cpu.
My question is:
For any new sql server or instance installation, should I use standard or enterprise edition of sql server. Which one will help to save money? I think enterprise edition is move expensive but gives benefits in vm environment when we have multiple instances on one server (vm).
Please help.
Thanks
Hi,
Newbie question. if this is not the right forum, let me know (I'm sure someone will!) SQL SERVER 2012 - I cannot create a foreign key. Error is:
Unable to create relationship 'FK_tblPersonnel_tblCompany'.
The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_tblPersonnel_tblCompany". The conflict occurred in database "WellService2_BE", table "dbo.tblCompany", column 'CompanyPK'.
Problem is, I cannot find the constraint at all - see query output attached. Looked at every key, index, constraint - cannot find one with that name. CompanyPK is the primary key in tblCompany
Thank you -
Hi all,
I am unable to get the Indian Standard DateTime without based on System DateTime in sql server 2008 r2.
Can you please solve my problem.
Thanks in advance
I have a SQL server database using SQL Server 2008.
I had an update performance issue and found that it block by a stored procedure select SQL.
I put with (NOLOCK) on the stored procedure and the issue is resolved.
My question is should I have NOLOCK every where on the entire application and what will be impact, will my database have better performance if I have NOLOCK every where in the database stored procedures?
I learn use SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED can have entire database NOLOCK for all select clause.
I did it on my database, but I do not see any improvement for the database application.
Your information and help is great appreciated,
Regards,
Souris,
Hello,
My database shutdown due to error 9002, instead of get in the read-only mode.
The error message is :
04/12/2013 16:34:15,spid169,Unknown,Database BizTalkMsgBoxDb was
shutdown due to error 9002 in routine 'XdesRMReadWrite::RollbackToLsn'.
Restart for non-snapshot databases will be attempted after all
connections to the database are aborted.
We are looking for what could cause this shutdown ?
Any clue ?
Thanks for you help. Regards. Etienne.
I have a table that gets inserted into several times a day. The current archive process thats in place does not include this table and it has almost a million rows in it, along with several indexes.
Which could likely be the culprit for poor insert times, the indexes or the fat that its a large table?
This article shows how to "unmask" the sql query behind a FECTH API_CUSOR
http://www.sqlskills.com/blogs/joe/hunting-down-the-origins-of-fetch-api_cursor-and-sp_cursorfetch/
that is shown in a deadlock graph. But if only applies if one can capture the event while it is ongoing. Is there a counter in Sql profier (2005) to indicate\capture the query behind the FETCH? (because most of the time I find out about deadlocks long after the victim spid has been killed.)
TIA,
edm2
P.S.Of course it I captured every sql statement executed on the server that may do it but I'm trying not to overburden the server by collecting excessive info
Hi,
We are facing some slower DB restoration in one of the production Server. Is there any best method, where we can to reduce DB restoration ?
Let me give overview :
Server Overview:
SQL Server 2008 R2 – Enterprise edition.
DB : Simple recovery model
Ram : 1 TB
Server - DL980 (fast track architecture)
Thanks,
Dhanapal
I have Altiris application database on sql server 2008 R2. user is requesting to find out performance issue on database.
I need to know how to troubleshoot for perticular database performance issue or what parameters should i use?
Hi,
I have a program in C# that I used to run on Visual Studio 2000 and SQL Server 2000 without any problem.
Now I upgrade to VS2005 and SQL Server 2005 and get and exception while
insert via SqlCommand.ExecuteNonQuery(). the insert is after many inserts to the same table by that program. the CommandTimeout is set to 600 (in the 2000 version I never had to change the default value of 30 seconds).
the insert is through a connection that is kept open throughout the program for more than 30 minutes
the exception message is:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
the trace is:
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(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
Thanks for your help !