Viewing 15 posts - 166 through 180 (of 231 total)
You can do that by joining the same table twice using ur primary key ( sequence number )
Select current.*,next_seq.*
From tableA current, tableA next_seq
where current.sol_sub_cat_Id+1 = next_seq.sol_sub_cat_Id
January 20, 2010 at 8:33 pm
This can help
http://www.sqlservercentral.com/Forums/Topic531822-360-1.aspx"> http://www.sqlservercentral.com/Forums/Topic531822-360-1.aspx
January 20, 2010 at 8:23 pm
There is some other transaction which is holding locks on the object your query wants.
Look into sp_lock and find whether any other transaction accessing the same table and holds...
January 20, 2010 at 7:42 pm
Right click on the database in SSMS , tasks->export/import wizard->export to excel.
January 19, 2010 at 12:05 am
Glad it worked..Welcome..our pleasure 🙂
January 18, 2010 at 7:04 pm
Ninja,
I have also used sp_start_job many times but not with linked servers.
So only didnt confirm it.;-)
January 17, 2010 at 8:03 pm
OSQL is depreciated and will be removed in future versions.
XP_cmdshell is always a security concern.
Both of these shd be used as last options.
If you have a pressing need to use...
January 17, 2010 at 6:51 pm
On server A on on success you can start other server job using
'sp_start_job'.
Create a linked server from Server A to Server B.
Map your agent accounts.
If ur linked server name...
January 16, 2010 at 9:09 pm
xparmanand,
Perhaps this one can be a useful read
http://strictlysql.blogspot.com/2009/07/impact-of-indexes-on-locking.html
Forgive me if you are already aware of it.
January 16, 2010 at 8:20 pm
You can also refer to the link below for identifying page splits
http://strictlysql.blogspot.com/2009/10/identifying-page-splits.html"> http://strictlysql.blogspot.com/2009/10/identifying-page-splits.html
January 12, 2010 at 8:50 pm
Just forgot to add if its less than 95% then yes its a memory crunch for sure. Ideal value is 99%
January 12, 2010 at 2:42 am
probably you are facing a memory crunch. Can you check the following?
under performance monitor(perfmon ) check the counter 'SQL Server Buffer: Buffer Cache Hit Ratio' for half an hour and...
January 12, 2010 at 2:39 am
On your problem, the issue looks awefully to close to the scenario I explained. Anyways will think of other possiblities as well.
January 5, 2010 at 1:06 am
Just to set things straight, MSSQL doesnt create unique temp table names WITHIN the SAME CONNECTION automatically.
This piece of code is for your ref
Create proc inner_sp
as
create table #tbl(col1 int )
Insert...
January 5, 2010 at 1:04 am
* On the same connection do u have any other temporary table with
the name #tbl.
A likely scenario can be this:
Your stored...
January 5, 2010 at 12:34 am
Viewing 15 posts - 166 through 180 (of 231 total)