Viewing 15 posts - 181 through 195 (of 308 total)
Hey, welcome to the forum.
This site has some great resources called stairways. Have a look at this one:-
http://www.sqlservercentral.com/stairway/75773/
It's called Stairway to T-SQL DML. That's Transact-SQL the flavour of SQL that...
September 3, 2014 at 1:35 pm
The master database contains all instance level information so logins, endpoints, linked servers etc.
Best way forward (imho) is to completely review your existing instance, script out or make a note...
September 3, 2014 at 1:30 pm
If you are just concerned about logins then I wouldn't but are you worried about anything in particular?
September 3, 2014 at 1:13 pm
GilaMonster (9/3/2014)
AppSup_dba (9/2/2014)
DB size - 300GB
Log drive size 100GB.
VLF count 750.
growth rate 1000MB
And take 2-3...
September 3, 2014 at 6:38 am
I don't think such a baseline will exist. The time taken to set the cluster and install SQL will entirely depend on your environment.
September 3, 2014 at 3:24 am
Hi Gary,
1. You can use SSMS 2014 to manage 2012 & 2008 R2 instances but I have had some problems connecting to 2005 instances.
2. I've got SSMS 2014 on my...
September 3, 2014 at 3:16 am
Your database is going into recovery mode probably because of some form of corruption.
Have you run DBCC CHECKDB recently?
September 3, 2014 at 3:08 am
The database is rolling back any active transactions by going through the VLFs in the transaction log, the time taken is based on the operations that have to be performed...
September 3, 2014 at 3:04 am
The best approach would be to prevent the transaction log of the database becoming full.
Are you running regular transaction log backups?
September 3, 2014 at 2:36 am
Are you still getting the same error once the table was removed from replication and the stored procedure executed?
September 2, 2014 at 6:56 am
What you could do is use mirroring or log shipping to perform your migration, you could backup & restore your database(s) onto the new server before you intend to migrate....
September 2, 2014 at 6:48 am
Have a look at this thread:- http://www.dbtalk.net/microsoft-public-sqlserver-replication/orphaned-entries-sys-objects-after-286901.html
It mentions using the following procedure after the table has been removed from replication:-
EXEC sp_MSunmarkreplinfo 'YOUR TABLE NAME';
GO
September 2, 2014 at 6:37 am
First place I'd be looking is the log within Management Studio. If you don't have access then look in the locations that Perry mentioned.
September 2, 2014 at 5:15 am
Instead of [Microsoft Query], can you use [From SQL Server] as the data source?
September 2, 2014 at 5:13 am
The error suggests that the connection string is defining Datacube_Prog10 as a server name.
The first thing I would do would be to go through the connection string and ensure the...
September 2, 2014 at 4:41 am
Viewing 15 posts - 181 through 195 (of 308 total)