Viewing 15 posts - 1,126 through 1,140 (of 1,335 total)
In SQL Server you can use the 3 or 4 part naming convention.
LINKEDSERVER.DATABASENAME.OWNERNAME.OBJECTNAME for REMOTESERVER
DATABASENAME.OWNER.OBJECTNAME for LOCAL SERVER DBs.
June 15, 2007 at 4:47 am
SPID keeps changing. An unallocated SPID used in past can be assigned to another user. Unless you have any moethods of logging enabled you will not able to track the...
June 15, 2007 at 4:46 am
INNER LOOP join is same as the JOIN but it forces a nested loop join to occur instead of a hash/merge join. I read this in a blog and used...
June 15, 2007 at 4:14 am
Check in TechNet there are beautiful documnets for both security and securely deploying a SQL Server application. The y will give you data as much as needed.
June 15, 2007 at 4:04 am
Go for logshipping. Yo can save ur logs files with it.
June 15, 2007 at 2:43 am
Is remote connection enabled. I hope they are by default disabled in SQL express version.
June 15, 2007 at 2:31 am
All the columns used in the join are indexed. Infact the execution plan was showing a hash join and i have forced it to be a nested join using inner...
June 15, 2007 at 2:11 am
Minaz,
I shall read the link and follow suggestion given there. Is it poosible to see exactly which part in a query needs to be tuned.
June 15, 2007 at 1:23 am
Can you post us the error message that you get while it is executed as a job?
June 15, 2007 at 1:14 am
Why not considering to archive to a history table. By this way you ensure you have a table in your database that has history records and can be accessed whenever...
June 15, 2007 at 12:50 am
After you restore you need to remove/resolve orphan users. that might be the reason why you dint get permissions at first.
June 15, 2007 at 12:24 am
Is firewall enabled between those servers. That might be one of the reasons. Also try giving the UNC path and check if you are able to perform the same successfully.
June 14, 2007 at 7:29 am
I don't think so just using /3GB switch will make sql to use more than 2 GB of ram. You should enable AWE also at the SQL Server level for...
June 14, 2007 at 7:23 am
If you have a connection that has executed and is not runnable you can check the coomand that it has executed and kill the spid. But check twice before you...
June 14, 2007 at 7:03 am
Check the target server memory and total server memory. Might be a memory problem too. Check how much you r sql server is using. Each connection takes few memory for...
June 14, 2007 at 6:57 am
Viewing 15 posts - 1,126 through 1,140 (of 1,335 total)