Viewing 15 posts - 31 through 45 (of 66 total)
Hi
It seems that the SSMS thought that the new login was already created and mapped to a user that was member of db_owner group. So, when you set it to...
July 22, 2015 at 4:39 am
Hi,
Maybe you also check the current QUOTED_IDENTIFIER set in the user connection configuration.
SET QUOTED_IDENTIFIER (Transact-SQL)
July 20, 2015 at 3:25 am
Hi.
Here is a complete series of articles about how to manage and work with AG in case you did not know it.
http://sqlmag.com/blog/alwayson-availability-groups-and-sql-server-jobs-part-1-introduction
I hope that it will give some good tips.
July 17, 2015 at 9:15 am
Hi,
Time ago I made for a customer a series of scripts that basically collected all remarkable system objects storing the results on an accessory DB and then I replicate this...
July 17, 2015 at 5:36 am
Hi,
Well It will depend on different factors like if the site is configured to absorb all users from both coasts and how many messages will cross between clients and server...
July 17, 2015 at 3:20 am
Hi,
It seems that this is a bug. This post relates almost the same issue that yours.
Regards
July 17, 2015 at 3:08 am
Hi,
Maybe this is a long workaround but, in order to play it safe, would this workaround suitable for your issue?
1.- Stop SQL Server service.
2.- Perform a cold copy of the...
July 13, 2015 at 3:43 am
Hi,
Have you tried to force a build/version verification in the package execution option step?
I hope this helps.
July 13, 2015 at 3:26 am
Hi,
Maybe this couple of articles will help you to troubleshoot the problem:
Some known issues with SQL Server Management Studio (SSMS)
http://thesqldude.com/2012/09/13/some-known-issues-with-sql-server-management-studio-ssms/[/url]
SSMS 2012 freezes when being launched
July 8, 2015 at 7:19 am
Hi,
Casually I heard just the opposite yesterday. SQL Server query engine uses additional resources to detect the use of NULLs while ANSI_NULL is set to OFF
Here is a good example...
July 7, 2015 at 5:51 am
As my colleague said SQL Server error log should give more hints.
The c0000005 error is a memory access violation error caused during service start up. Error log may point...
July 6, 2015 at 5:11 am
Hi alpenit,
Best option for you should be to perform a side-by-side migration. Basically, you have to install a new Windows OS with a SQL Server and then migrate all instance...
July 6, 2015 at 3:48 am
Just curious,
Does the DB access to a CLR stored procedures or has any network latency issues?
July 3, 2015 at 3:45 am
Hi,
FILESTREAM by design will perform better with C# or any other language that uses OS API to access to the data. As you said, T-SQL is an interpreted language but...
July 3, 2015 at 3:39 am
Hi,
Please check this KB if this case suits to your current issue even if it is a SQL Server 2008R2
https://support.microsoft.com/en-us/kb/2163980
Other troubleshoot option would be these ones
July 3, 2015 at 3:28 am
Viewing 15 posts - 31 through 45 (of 66 total)