Hi, could someone give me some general pointers on why an application would
fail after an sql upgrade from 6.5 -> 7 or 7 -> 2000.
What are some of the reasons/causes an application would not become
compatible with an upgrade of sql. Are there any references/resources on
this?
Thanks!
PeterPeter,
There is a large Backward Compatability section in the BOL. Online it can
be found at:
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/tsqlref/ts_sa-ses_9sfo.asp
Also there is a section on New and Enhanced Features in Transact-SQL.
Online this is at:
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/tsqlref/ts_sa-ses_9sfo.asp
Hope that these help.
Russell Fields
"Hz" <Hz@.nospam.com> wrote in message
news:flmAb.4463$xm.141272@.nasal.pacific.net.au...
> Hi, could someone give me some general pointers on why an application
would
> fail after an sql upgrade from 6.5 -> 7 or 7 -> 2000.
> What are some of the reasons/causes an application would not become
> compatible with an upgrade of sql. Are there any references/resources on
> this?
> Thanks!
> Peter
>|||Russell gave some good links, but in the end,
functionality, code calls, and syntax can change.
Plus, DB-Lib, which was (pre-7.0) the preferred method of
connecting to SQL Server, is no longer that way from 7.0
on, and newer features cannot be used with DB-Lib.
The application must be tested PRIOR to upgrading to fix
any problems in a test environment.
>--Original Message--
>Hi, could someone give me some general pointers on why an
application would
>fail after an sql upgrade from 6.5 -> 7 or 7 -> 2000.
>What are some of the reasons/causes an application would
not become
>compatible with an upgrade of sql. Are there any
references/resources on
>this?
>Thanks!
>Peter
>
>.
>|||Thanks for the pointers, they are much appreciated!
Peter
"Allan Hirt" <allanh@.NOSPAMavanade.com> wrote in message
news:e49301c3bc25$181fb990$a601280a@.phx.gbl...
> Russell gave some good links, but in the end,
> functionality, code calls, and syntax can change.
> Plus, DB-Lib, which was (pre-7.0) the preferred method of
> connecting to SQL Server, is no longer that way from 7.0
> on, and newer features cannot be used with DB-Lib.
> The application must be tested PRIOR to upgrading to fix
> any problems in a test environment.
> >--Original Message--
> >Hi, could someone give me some general pointers on why an
> application would
> >fail after an sql upgrade from 6.5 -> 7 or 7 -> 2000.
> >
> >What are some of the reasons/causes an application would
> not become
> >compatible with an upgrade of sql. Are there any
> references/resources on
> >this?
> >
> >Thanks!
> >Peter
> >
> >
> >.
> >
Showing posts with label due. Show all posts
Showing posts with label due. Show all posts
Friday, February 24, 2012
Thursday, February 16, 2012
Append query from Access Table to Linked SQL Server Table Failing
Strange one here - I am posting this in both SQL Server and Access forums
Access is telling me it can't append any of the records due to a key violation.
The query:
INSERT INTO dbo_Colors ( NameColorID, Application, Red, Green, Blue )
SELECT Colors_Access.NameColorID, Colors_Access.Application, Colors_Access.Red, Colors_Access.Green, Colors_Access.Blue
FROM Colors_Access;
Colors_Access is linked from another MDB and dbo_Colors is linked from SQL Server 2000.
There are no indexes or foreign contraints on the SQL table. I have no relationships on the dbo_ table in my MDB. The query works if I append to another Access table. The datatypes all match between the two tables though the dbo_ tables has two additional fields not refrenced in the query.
I can manually append the records using cut and paste with no problems.
I have tried re-linking the tables.
Any ideas?
Thanks,
BradI'd guess that the SQL Server db you think you are linking to in dbo_Colors isn't really the one you think. Perhaps the login/password in your datasource is connecting to a different database than the one you expect?
To check, get the name of the constraint being violated and check in the sql server table to see if that constraint exists
Also, try running the sql server profiler to see what sql server db ms access is trying to insert data into|||mattrevs,
It does appear that I am linking the right table. There is only one Colors table and only one database that has a colors table.
Could you tell me how to check which constraint is being violated? After I manually pasted the data into dbo_Colors, I ran checkconstraints() and no error were reported.
I also tried running the query with implicit_transaction OFF and still no joy.
I ran the trace and here are the last two lines. The first one was simply duplicated for each record:
RPC:Completed exec sp_executesql N'INSERT INTO "dbo"."Colors" ("NameColorID","Application","Red","Green","Blue") VALUES (@.P1,@.P2,@.P3,@.P4,@.P5)', N'@.P1 nvarchar(38),@.P2 nvarchar(30),@.P3 int,@.P4 int,@.P5 int', N'{FFC28EAD-1134-40BB-9723-7D88A0B0AC7A}', N'Tile1', 197, 183, 156 Microsoft Access sa 0 11 0 0 2564 54 2004-06-21 10:35:14.170
SQL:BatchCompleted IF @.@.TRANCOUNT > 0 ROLLBACK TRAN Microsoft Access sa 0 0 0 0 2564 54 2004-06-21 10:35:19.403
- Brad|||You say that pasting the data one row at a time from within ms access works ok?
If so, maybe you could also perform a sql trace on this and see what is different?|||I got it figured out. (BTW, I did the trace with the pasting but the results were ... confusing)
Apparently a bit field in SQL server can be Null?
There are two additional fields in the SQL version of the table. The NVarChar field I had set to allow nulls. I never bothered with the Bit field.
When I checked Allow Nulls on the bit field and re-linked, my query worked.
I guess my lesson her is never assume anything. I have learned that lesson many times and will probably learn it again in the (near) future.
Thanks for your help,
Brad
Access is telling me it can't append any of the records due to a key violation.
The query:
INSERT INTO dbo_Colors ( NameColorID, Application, Red, Green, Blue )
SELECT Colors_Access.NameColorID, Colors_Access.Application, Colors_Access.Red, Colors_Access.Green, Colors_Access.Blue
FROM Colors_Access;
Colors_Access is linked from another MDB and dbo_Colors is linked from SQL Server 2000.
There are no indexes or foreign contraints on the SQL table. I have no relationships on the dbo_ table in my MDB. The query works if I append to another Access table. The datatypes all match between the two tables though the dbo_ tables has two additional fields not refrenced in the query.
I can manually append the records using cut and paste with no problems.
I have tried re-linking the tables.
Any ideas?
Thanks,
BradI'd guess that the SQL Server db you think you are linking to in dbo_Colors isn't really the one you think. Perhaps the login/password in your datasource is connecting to a different database than the one you expect?
To check, get the name of the constraint being violated and check in the sql server table to see if that constraint exists
Also, try running the sql server profiler to see what sql server db ms access is trying to insert data into|||mattrevs,
It does appear that I am linking the right table. There is only one Colors table and only one database that has a colors table.
Could you tell me how to check which constraint is being violated? After I manually pasted the data into dbo_Colors, I ran checkconstraints() and no error were reported.
I also tried running the query with implicit_transaction OFF and still no joy.
I ran the trace and here are the last two lines. The first one was simply duplicated for each record:
RPC:Completed exec sp_executesql N'INSERT INTO "dbo"."Colors" ("NameColorID","Application","Red","Green","Blue") VALUES (@.P1,@.P2,@.P3,@.P4,@.P5)', N'@.P1 nvarchar(38),@.P2 nvarchar(30),@.P3 int,@.P4 int,@.P5 int', N'{FFC28EAD-1134-40BB-9723-7D88A0B0AC7A}', N'Tile1', 197, 183, 156 Microsoft Access sa 0 11 0 0 2564 54 2004-06-21 10:35:14.170
SQL:BatchCompleted IF @.@.TRANCOUNT > 0 ROLLBACK TRAN Microsoft Access sa 0 0 0 0 2564 54 2004-06-21 10:35:19.403
- Brad|||You say that pasting the data one row at a time from within ms access works ok?
If so, maybe you could also perform a sql trace on this and see what is different?|||I got it figured out. (BTW, I did the trace with the pasting but the results were ... confusing)
Apparently a bit field in SQL server can be Null?
There are two additional fields in the SQL version of the table. The NVarChar field I had set to allow nulls. I never bothered with the Bit field.
When I checked Allow Nulls on the bit field and re-linked, my query worked.
I guess my lesson her is never assume anything. I have learned that lesson many times and will probably learn it again in the (near) future.
Thanks for your help,
Brad
AppDomain unloads due to memory pressure.
We deployed a new SQL Server 2005 production server 6 weeks ago. This
server has 8 GB memory and is configured with AWE enabled, 6656 MB max
server memory and /3GB switch.
Twice for the last 2 weeks we had a situation when CPU time went up
and all users reported a significant system slowdown.
Every 30 seconds these messages were logged in the error log:
AppDomain 29 (master.dbo[runtime].28) is marked for unload due to
memory pressure.
AppDomain 29 (master.dbo[runtime].28) unloaded.
AppDomain 30 (master.dbo[runtime].29) created.
sys.dm_exec_cached_plans view had only few records, so I assume the
procedure cache was flushed with every AppDomain unload.
This is the memory snapshot at the time:
Memory Manager KB
-- --
VM Reserved 2802932
VM Committed 141204
AWE Allocated 6821176
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2798772
VM Committed 137196
AWE Allocated 6821176
MultiPage Allocator 33384
SinglePage Allocator 64904
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2612332
VM Committed 69032
AWE Allocated 6821176
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 1280
MultiPage Allocator 1488
Buffer Distribution Buffers
-- --
Stolen 4568
Free 40186
Cached 3545
Database (clean) 699081
Database (dirty) 104587
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 803669
Stolen Potential 293455
External Reservation 0
Min Free 1872
Visible 317440
Available Paging File 578065
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 7
TotalPages 92
InUsePages 42
This is the memory snapshot during the regular load:
Memory Manager KB
-- --
VM Reserved 2795508
VM Committed 130708
AWE Allocated 6815904
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2791348
VM Committed 126700
AWE Allocated 6815904
MultiPage Allocator 21296
SinglePage Allocator 1506648
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2620524
VM Committed 69032
AWE Allocated 6815904
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 135936
VM Committed 23900
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 880
MultiPage Allocator 1232
Buffer Distribution Buffers
-- --
Stolen 8073
Free 11148
Cached 180258
Database (clean) 627780
Database (dirty) 24708
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 652489
Stolen Potential 114209
External Reservation 0
Min Free 1008
Visible 318464
Available Paging File 581447
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 29506
TotalPages 176205
InUsePages 2795
Both times the server reboot has fixed the problem.
I'm just wondering if this is an indication of CLR related memory
leaking or the problem is with SQL Server 2005 memory allocation/
management that forces AppDomain unloads?
Do I still need to reboot the server in order to fix it or I can just
run DBCC FREESYSTEMCACHE?
Is there a way to prevent this from happening?
Thanks.
On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
> We deployed a new SQL Server 2005 production server 6 weeks ago. This
> server has 8 GBmemoryand is configured with AWE enabled, 6656 MB max
> servermemoryand /3GB switch.
[...]
> Every 30 seconds these messages were logged in the error log:AppDomain29 (master.dbo[runtime].28) ismarkedforunloadduetomemorypressure.AppDomain29 (master.dbo[runtime].28) unloaded.AppDomain30 (master.dbo[runtime].29) created.
I am having something similar happen.
I found this, which doesn't directly apply to me (we're on SP2, so it
should be fixed), but we are getting those messages as well.
http://support.microsoft.com/kb/917271
However, at least one other person is having this happen:
[url]http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/78717b6a0452847a/ad371baa9fa12a4d?hl=en&lnk=st&q=AppDomain+is+marke d+for+unload+due+to+memory+pressure.#ad371baa9fa12 a4d[/url]
It says user defined datatypes and CLR, and mine has a specific
database name, so that's where I'm looking first. Will post more as I
find it.
|||On Dec 4, 3:03 pm, bour...@.gmail.com wrote:
> On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
> [...]
> I am having something similar happen.
> I found this, which doesn't directly apply to me (we're on SP2, so it
> should be fixed), but we are getting those messages as well.http://support.microsoft.com/kb/917271
> However, at least one other person is having this happen:http://groups.google.com/group/microsoft.public.sqlserver.server/brow...
> It says user defined datatypes and CLR, and mine has a specific
> database name, so that's where I'm looking first. Will post more as I
> find it.
We are also running SP2. The message is related to master since the
CLR assembly is created in master. It happens once in 3 days now
during the pick hours. DBCC FREESYSTEMCACHE doesn't help at all, only
reboot.
Opened a ticket with Microsoft but they have no idea what's happening.
Asked me to run PSSDiag and send a result to them.
These are the performance counters related to memory when the issue
occurs:
Memory: Available Bytes: 602,260,000
Memory: Pages/sec: 0
Process: Working Set Total: 778,264,576
Process: Working Set SQL Server: 262,144,000
SQL Server: Buffer Manager: Buffer Cache Hit Ratio: 99.851
SQL Server: Buffer Manager: Total Pages: 851,968
SQL Server: Memory Manager: Total Server Memory (KB): 6,815,744
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
There is no any other processes running on the server at the time.
Don't see any memory pressure.
This is really frustrating since it was running on a less powerful
hardware with 3GB RAM with SQL Server 2000 just 2 months ago with no
issues.
I really need help with this one.
Thanks,
Vlad
server has 8 GB memory and is configured with AWE enabled, 6656 MB max
server memory and /3GB switch.
Twice for the last 2 weeks we had a situation when CPU time went up
and all users reported a significant system slowdown.
Every 30 seconds these messages were logged in the error log:
AppDomain 29 (master.dbo[runtime].28) is marked for unload due to
memory pressure.
AppDomain 29 (master.dbo[runtime].28) unloaded.
AppDomain 30 (master.dbo[runtime].29) created.
sys.dm_exec_cached_plans view had only few records, so I assume the
procedure cache was flushed with every AppDomain unload.
This is the memory snapshot at the time:
Memory Manager KB
-- --
VM Reserved 2802932
VM Committed 141204
AWE Allocated 6821176
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2798772
VM Committed 137196
AWE Allocated 6821176
MultiPage Allocator 33384
SinglePage Allocator 64904
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2612332
VM Committed 69032
AWE Allocated 6821176
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 1280
MultiPage Allocator 1488
Buffer Distribution Buffers
-- --
Stolen 4568
Free 40186
Cached 3545
Database (clean) 699081
Database (dirty) 104587
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 803669
Stolen Potential 293455
External Reservation 0
Min Free 1872
Visible 317440
Available Paging File 578065
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 7
TotalPages 92
InUsePages 42
This is the memory snapshot during the regular load:
Memory Manager KB
-- --
VM Reserved 2795508
VM Committed 130708
AWE Allocated 6815904
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2791348
VM Committed 126700
AWE Allocated 6815904
MultiPage Allocator 21296
SinglePage Allocator 1506648
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2620524
VM Committed 69032
AWE Allocated 6815904
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 135936
VM Committed 23900
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 880
MultiPage Allocator 1232
Buffer Distribution Buffers
-- --
Stolen 8073
Free 11148
Cached 180258
Database (clean) 627780
Database (dirty) 24708
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 652489
Stolen Potential 114209
External Reservation 0
Min Free 1008
Visible 318464
Available Paging File 581447
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 29506
TotalPages 176205
InUsePages 2795
Both times the server reboot has fixed the problem.
I'm just wondering if this is an indication of CLR related memory
leaking or the problem is with SQL Server 2005 memory allocation/
management that forces AppDomain unloads?
Do I still need to reboot the server in order to fix it or I can just
run DBCC FREESYSTEMCACHE?
Is there a way to prevent this from happening?
Thanks.
On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
> We deployed a new SQL Server 2005 production server 6 weeks ago. This
> server has 8 GBmemoryand is configured with AWE enabled, 6656 MB max
> servermemoryand /3GB switch.
[...]
> Every 30 seconds these messages were logged in the error log:AppDomain29 (master.dbo[runtime].28) ismarkedforunloadduetomemorypressure.AppDomain29 (master.dbo[runtime].28) unloaded.AppDomain30 (master.dbo[runtime].29) created.
I am having something similar happen.
I found this, which doesn't directly apply to me (we're on SP2, so it
should be fixed), but we are getting those messages as well.
http://support.microsoft.com/kb/917271
However, at least one other person is having this happen:
[url]http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/78717b6a0452847a/ad371baa9fa12a4d?hl=en&lnk=st&q=AppDomain+is+marke d+for+unload+due+to+memory+pressure.#ad371baa9fa12 a4d[/url]
It says user defined datatypes and CLR, and mine has a specific
database name, so that's where I'm looking first. Will post more as I
find it.
|||On Dec 4, 3:03 pm, bour...@.gmail.com wrote:
> On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
> [...]
> I am having something similar happen.
> I found this, which doesn't directly apply to me (we're on SP2, so it
> should be fixed), but we are getting those messages as well.http://support.microsoft.com/kb/917271
> However, at least one other person is having this happen:http://groups.google.com/group/microsoft.public.sqlserver.server/brow...
> It says user defined datatypes and CLR, and mine has a specific
> database name, so that's where I'm looking first. Will post more as I
> find it.
We are also running SP2. The message is related to master since the
CLR assembly is created in master. It happens once in 3 days now
during the pick hours. DBCC FREESYSTEMCACHE doesn't help at all, only
reboot.
Opened a ticket with Microsoft but they have no idea what's happening.
Asked me to run PSSDiag and send a result to them.
These are the performance counters related to memory when the issue
occurs:
Memory: Available Bytes: 602,260,000
Memory: Pages/sec: 0
Process: Working Set Total: 778,264,576
Process: Working Set SQL Server: 262,144,000
SQL Server: Buffer Manager: Buffer Cache Hit Ratio: 99.851
SQL Server: Buffer Manager: Total Pages: 851,968
SQL Server: Memory Manager: Total Server Memory (KB): 6,815,744
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
There is no any other processes running on the server at the time.
Don't see any memory pressure.
This is really frustrating since it was running on a less powerful
hardware with 3GB RAM with SQL Server 2000 just 2 months ago with no
issues.
I really need help with this one.
Thanks,
Vlad
Monday, February 13, 2012
AppDomain unloads due to memory pressure.
We deployed a new SQL Server 2005 production server 6 weeks ago. This
server has 8 GB memory and is configured with AWE enabled, 6656 MB max
server memory and /3GB switch.
Twice for the last 2 weeks we had a situation when CPU time went up
and all users reported a significant system slowdown.
Every 30 seconds these messages were logged in the error log:
AppDomain 29 (master.dbo[runtime].28) is marked for unload due to
memory pressure.
AppDomain 29 (master.dbo[runtime].28) unloaded.
AppDomain 30 (master.dbo[runtime].29) created.
sys.dm_exec_cached_plans view had only few records, so I assume the
procedure cache was flushed with every AppDomain unload.
This is the memory snapshot at the time:
Memory Manager KB
-- --
VM Reserved 2802932
VM Committed 141204
AWE Allocated 6821176
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2798772
VM Committed 137196
AWE Allocated 6821176
MultiPage Allocator 33384
SinglePage Allocator 64904
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2612332
VM Committed 69032
AWE Allocated 6821176
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 1280
MultiPage Allocator 1488
Buffer Distribution Buffers
-- --
Stolen 4568
Free 40186
Cached 3545
Database (clean) 699081
Database (dirty) 104587
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 803669
Stolen Potential 293455
External Reservation 0
Min Free 1872
Visible 317440
Available Paging File 578065
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 7
TotalPages 92
InUsePages 42
This is the memory snapshot during the regular load:
Memory Manager KB
-- --
VM Reserved 2795508
VM Committed 130708
AWE Allocated 6815904
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2791348
VM Committed 126700
AWE Allocated 6815904
MultiPage Allocator 21296
SinglePage Allocator 1506648
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2620524
VM Committed 69032
AWE Allocated 6815904
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 135936
VM Committed 23900
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 880
MultiPage Allocator 1232
Buffer Distribution Buffers
-- --
Stolen 8073
Free 11148
Cached 180258
Database (clean) 627780
Database (dirty) 24708
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 652489
Stolen Potential 114209
External Reservation 0
Min Free 1008
Visible 318464
Available Paging File 581447
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 29506
TotalPages 176205
InUsePages 2795
Both times the server reboot has fixed the problem.
I'm just wondering if this is an indication of CLR related memory
leaking or the problem is with SQL Server 2005 memory allocation/
management that forces AppDomain unloads?
Do I still need to reboot the server in order to fix it or I can just
run DBCC FREESYSTEMCACHE?
Is there a way to prevent this from happening?
Thanks.On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
> We deployed a new SQL Server 2005 production server 6 weeks ago. This
> server has 8 GBmemoryand is configured with AWE enabled, 6656 MB max
> servermemoryand /3GB switch.
[...]
> Every 30 seconds these messages were logged in the error log:AppDomain29 (master.d
bo[runtime].28) ismarkedforunloadduetomemorypressure.AppDomain29 (master.dbo[
;runtime].28) unloaded.AppDomain30 (master.dbo[runtime].29) created.
I am having something similar happen.
I found this, which doesn't directly apply to me (we're on SP2, so it
should be fixed), but we are getting those messages as well.
http://support.microsoft.com/kb/917271
However, at least one other person is having this happen:
http://groups.google.com/group/micr...d371baa9fa12a4d
It says user defined datatypes and CLR, and mine has a specific
database name, so that's where I'm looking first. Will post more as I
find it.|||On Dec 4, 3:03 pm, bour...@.gmail.com wrote:
> On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
>
> [...]
> I am having something similar happen.
> I found this, which doesn't directly apply to me (we're on SP2, so it
> should be fixed), but we are getting those messages as well.http://support.micro
soft.com/kb/917271
> However, at least one other person is having this happen:http://groups.google.co
m/gr...server/brow...
> It says user defined datatypes and CLR, and mine has a specific
> database name, so that's where I'm looking first. Will post more as I
> find it.
We are also running SP2. The message is related to master since the
CLR assembly is created in master. It happens once in 3 days now
during the pick hours. DBCC FREESYSTEMCACHE doesn't help at all, only
reboot.
Opened a ticket with Microsoft but they have no idea what's happening.
Asked me to run PSSDiag and send a result to them.
These are the performance counters related to memory when the issue
occurs:
Memory: Available Bytes: 602,260,000
Memory: Pages/sec: 0
Process: Working Set Total: 778,264,576
Process: Working Set SQL Server: 262,144,000
SQL Server: Buffer Manager: Buffer Cache Hit Ratio: 99.851
SQL Server: Buffer Manager: Total Pages: 851,968
SQL Server: Memory Manager: Total Server Memory (KB): 6,815,744
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
There is no any other processes running on the server at the time.
Don't see any memory pressure.
This is really frustrating since it was running on a less powerful
hardware with 3GB RAM with SQL Server 2000 just 2 months ago with no
issues.
I really need help with this one.
Thanks,
Vlad
server has 8 GB memory and is configured with AWE enabled, 6656 MB max
server memory and /3GB switch.
Twice for the last 2 weeks we had a situation when CPU time went up
and all users reported a significant system slowdown.
Every 30 seconds these messages were logged in the error log:
AppDomain 29 (master.dbo[runtime].28) is marked for unload due to
memory pressure.
AppDomain 29 (master.dbo[runtime].28) unloaded.
AppDomain 30 (master.dbo[runtime].29) created.
sys.dm_exec_cached_plans view had only few records, so I assume the
procedure cache was flushed with every AppDomain unload.
This is the memory snapshot at the time:
Memory Manager KB
-- --
VM Reserved 2802932
VM Committed 141204
AWE Allocated 6821176
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2798772
VM Committed 137196
AWE Allocated 6821176
MultiPage Allocator 33384
SinglePage Allocator 64904
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2612332
VM Committed 69032
AWE Allocated 6821176
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 1280
MultiPage Allocator 1488
Buffer Distribution Buffers
-- --
Stolen 4568
Free 40186
Cached 3545
Database (clean) 699081
Database (dirty) 104587
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 803669
Stolen Potential 293455
External Reservation 0
Min Free 1872
Visible 317440
Available Paging File 578065
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 7
TotalPages 92
InUsePages 42
This is the memory snapshot during the regular load:
Memory Manager KB
-- --
VM Reserved 2795508
VM Committed 130708
AWE Allocated 6815904
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2791348
VM Committed 126700
AWE Allocated 6815904
MultiPage Allocator 21296
SinglePage Allocator 1506648
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2620524
VM Committed 69032
AWE Allocated 6815904
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 135936
VM Committed 23900
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 880
MultiPage Allocator 1232
Buffer Distribution Buffers
-- --
Stolen 8073
Free 11148
Cached 180258
Database (clean) 627780
Database (dirty) 24708
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 652489
Stolen Potential 114209
External Reservation 0
Min Free 1008
Visible 318464
Available Paging File 581447
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 29506
TotalPages 176205
InUsePages 2795
Both times the server reboot has fixed the problem.
I'm just wondering if this is an indication of CLR related memory
leaking or the problem is with SQL Server 2005 memory allocation/
management that forces AppDomain unloads?
Do I still need to reboot the server in order to fix it or I can just
run DBCC FREESYSTEMCACHE?
Is there a way to prevent this from happening?
Thanks.On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
> We deployed a new SQL Server 2005 production server 6 weeks ago. This
> server has 8 GBmemoryand is configured with AWE enabled, 6656 MB max
> servermemoryand /3GB switch.
[...]
> Every 30 seconds these messages were logged in the error log:AppDomain29 (master.d
bo[runtime].28) ismarkedforunloadduetomemorypressure.AppDomain29 (master.dbo[
;runtime].28) unloaded.AppDomain30 (master.dbo[runtime].29) created.
I am having something similar happen.
I found this, which doesn't directly apply to me (we're on SP2, so it
should be fixed), but we are getting those messages as well.
http://support.microsoft.com/kb/917271
However, at least one other person is having this happen:
http://groups.google.com/group/micr...d371baa9fa12a4d
It says user defined datatypes and CLR, and mine has a specific
database name, so that's where I'm looking first. Will post more as I
find it.|||On Dec 4, 3:03 pm, bour...@.gmail.com wrote:
> On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
>
> [...]
> I am having something similar happen.
> I found this, which doesn't directly apply to me (we're on SP2, so it
> should be fixed), but we are getting those messages as well.http://support.micro
soft.com/kb/917271
> However, at least one other person is having this happen:http://groups.google.co
m/gr...server/brow...
> It says user defined datatypes and CLR, and mine has a specific
> database name, so that's where I'm looking first. Will post more as I
> find it.
We are also running SP2. The message is related to master since the
CLR assembly is created in master. It happens once in 3 days now
during the pick hours. DBCC FREESYSTEMCACHE doesn't help at all, only
reboot.
Opened a ticket with Microsoft but they have no idea what's happening.
Asked me to run PSSDiag and send a result to them.
These are the performance counters related to memory when the issue
occurs:
Memory: Available Bytes: 602,260,000
Memory: Pages/sec: 0
Process: Working Set Total: 778,264,576
Process: Working Set SQL Server: 262,144,000
SQL Server: Buffer Manager: Buffer Cache Hit Ratio: 99.851
SQL Server: Buffer Manager: Total Pages: 851,968
SQL Server: Memory Manager: Total Server Memory (KB): 6,815,744
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
There is no any other processes running on the server at the time.
Don't see any memory pressure.
This is really frustrating since it was running on a less powerful
hardware with 3GB RAM with SQL Server 2000 just 2 months ago with no
issues.
I really need help with this one.
Thanks,
Vlad
AppDomain unloads due to memory pressure.
We deployed a new SQL Server 2005 production server 6 weeks ago. This
server has 8 GB memory and is configured with AWE enabled, 6656 MB max
server memory and /3GB switch.
Twice for the last 2 weeks we had a situation when CPU time went up
and all users reported a significant system slowdown.
Every 30 seconds these messages were logged in the error log:
AppDomain 29 (master.dbo[runtime].28) is marked for unload due to
memory pressure.
AppDomain 29 (master.dbo[runtime].28) unloaded.
AppDomain 30 (master.dbo[runtime].29) created.
sys.dm_exec_cached_plans view had only few records, so I assume the
procedure cache was flushed with every AppDomain unload.
This is the memory snapshot at the time:
Memory Manager KB
-- --
VM Reserved 2802932
VM Committed 141204
AWE Allocated 6821176
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2798772
VM Committed 137196
AWE Allocated 6821176
MultiPage Allocator 33384
SinglePage Allocator 64904
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2612332
VM Committed 69032
AWE Allocated 6821176
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 1280
MultiPage Allocator 1488
Buffer Distribution Buffers
-- --
Stolen 4568
Free 40186
Cached 3545
Database (clean) 699081
Database (dirty) 104587
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 803669
Stolen Potential 293455
External Reservation 0
Min Free 1872
Visible 317440
Available Paging File 578065
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 7
TotalPages 92
InUsePages 42
This is the memory snapshot during the regular load:
Memory Manager KB
-- --
VM Reserved 2795508
VM Committed 130708
AWE Allocated 6815904
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2791348
VM Committed 126700
AWE Allocated 6815904
MultiPage Allocator 21296
SinglePage Allocator 1506648
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2620524
VM Committed 69032
AWE Allocated 6815904
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 135936
VM Committed 23900
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 880
MultiPage Allocator 1232
Buffer Distribution Buffers
-- --
Stolen 8073
Free 11148
Cached 180258
Database (clean) 627780
Database (dirty) 24708
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 652489
Stolen Potential 114209
External Reservation 0
Min Free 1008
Visible 318464
Available Paging File 581447
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 29506
TotalPages 176205
InUsePages 2795
Both times the server reboot has fixed the problem.
I'm just wondering if this is an indication of CLR related memory
leaking or the problem is with SQL Server 2005 memory allocation/
management that forces AppDomain unloads?
Do I still need to reboot the server in order to fix it or I can just
run DBCC FREESYSTEMCACHE?
Is there a way to prevent this from happening?
Thanks.On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
> We deployed a new SQL Server 2005 production server 6 weeks ago. This
> server has 8 GBmemoryand is configured with AWE enabled, 6656 MB max
> servermemoryand /3GB switch.
[...]
> Every 30 seconds these messages were logged in the error log:AppDomain29 (master.dbo[runtime].28) ismarkedforunloadduetomemorypressure.AppDomain29 (master.dbo[runtime].28) unloaded.AppDomain30 (master.dbo[runtime].29) created.
I am having something similar happen.
I found this, which doesn't directly apply to me (we're on SP2, so it
should be fixed), but we are getting those messages as well.
http://support.microsoft.com/kb/917271
However, at least one other person is having this happen:
http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/78717b6a0452847a/ad371baa9fa12a4d?hl=en&lnk=st&q=AppDomain+is+marked+for+unload+due+to+memory+pressure.#ad371baa9fa12a4d
It says user defined datatypes and CLR, and mine has a specific
database name, so that's where I'm looking first. Will post more as I
find it.|||On Dec 4, 3:03 pm, bour...@.gmail.com wrote:
> On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
> > We deployed a new SQL Server 2005 production server 6 weeks ago. This
> > server has 8 GBmemoryand is configured with AWE enabled, 6656 MB max
> > servermemoryand /3GB switch.
> [...]
> > Every 30 seconds these messages were logged in the error log:AppDomain29 (master.dbo[runtime].28) ismarkedforunloadduetomemorypressure.AppDomain29 (master.dbo[runtime].28) unloaded.AppDomain30 (master.dbo[runtime].29) created.
> I am having something similar happen.
> I found this, which doesn't directly apply to me (we're on SP2, so it
> should be fixed), but we are getting those messages as well.http://support.microsoft.com/kb/917271
> However, at least one other person is having this happen:http://groups.google.com/group/microsoft.public.sqlserver.server/brow...
> It says user defined datatypes and CLR, and mine has a specific
> database name, so that's where I'm looking first. Will post more as I
> find it.
We are also running SP2. The message is related to master since the
CLR assembly is created in master. It happens once in 3 days now
during the pick hours. DBCC FREESYSTEMCACHE doesn't help at all, only
reboot.
Opened a ticket with Microsoft but they have no idea what's happening.
Asked me to run PSSDiag and send a result to them.
These are the performance counters related to memory when the issue
occurs:
Memory: Available Bytes: 602,260,000
Memory: Pages/sec: 0
Process: Working Set Total: 778,264,576
Process: Working Set SQL Server: 262,144,000
SQL Server: Buffer Manager: Buffer Cache Hit Ratio: 99.851
SQL Server: Buffer Manager: Total Pages: 851,968
SQL Server: Memory Manager: Total Server Memory (KB): 6,815,744
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
There is no any other processes running on the server at the time.
Don't see any memory pressure.
This is really frustrating since it was running on a less powerful
hardware with 3GB RAM with SQL Server 2000 just 2 months ago with no
issues.
I really need help with this one.
Thanks,
Vlad
server has 8 GB memory and is configured with AWE enabled, 6656 MB max
server memory and /3GB switch.
Twice for the last 2 weeks we had a situation when CPU time went up
and all users reported a significant system slowdown.
Every 30 seconds these messages were logged in the error log:
AppDomain 29 (master.dbo[runtime].28) is marked for unload due to
memory pressure.
AppDomain 29 (master.dbo[runtime].28) unloaded.
AppDomain 30 (master.dbo[runtime].29) created.
sys.dm_exec_cached_plans view had only few records, so I assume the
procedure cache was flushed with every AppDomain unload.
This is the memory snapshot at the time:
Memory Manager KB
-- --
VM Reserved 2802932
VM Committed 141204
AWE Allocated 6821176
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2798772
VM Committed 137196
AWE Allocated 6821176
MultiPage Allocator 33384
SinglePage Allocator 64904
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2612332
VM Committed 69032
AWE Allocated 6821176
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 1280
MultiPage Allocator 1488
Buffer Distribution Buffers
-- --
Stolen 4568
Free 40186
Cached 3545
Database (clean) 699081
Database (dirty) 104587
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 803669
Stolen Potential 293455
External Reservation 0
Min Free 1872
Visible 317440
Available Paging File 578065
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 7
TotalPages 92
InUsePages 42
This is the memory snapshot during the regular load:
Memory Manager KB
-- --
VM Reserved 2795508
VM Committed 130708
AWE Allocated 6815904
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
-- --
VM Reserved 2791348
VM Committed 126700
AWE Allocated 6815904
MultiPage Allocator 21296
SinglePage Allocator 1506648
MEMORYCLERK_SQLBUFFERPOOL (Total) KB
--- --
VM Reserved 2620524
VM Committed 69032
AWE Allocated 6815904
SM Reserved 0
SM Commited 0
SinglePage Allocator 0
MultiPage Allocator 2040
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 135936
VM Committed 23900
AWE Allocated 0
SM Reserved 0
SM Commited 0
SinglePage Allocator 880
MultiPage Allocator 1232
Buffer Distribution Buffers
-- --
Stolen 8073
Free 11148
Cached 180258
Database (clean) 627780
Database (dirty) 24708
I/O 0
Latched 1
(7 row(s) affected)
Buffer Counts Buffers
-- --
Committed 851968
Target 851968
Hashed 652489
Stolen Potential 114209
External Reservation 0
Min Free 1008
Visible 318464
Available Paging File 581447
(8 row(s) affected)
Procedure Cache Value
-- --
TotalProcs 29506
TotalPages 176205
InUsePages 2795
Both times the server reboot has fixed the problem.
I'm just wondering if this is an indication of CLR related memory
leaking or the problem is with SQL Server 2005 memory allocation/
management that forces AppDomain unloads?
Do I still need to reboot the server in order to fix it or I can just
run DBCC FREESYSTEMCACHE?
Is there a way to prevent this from happening?
Thanks.On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
> We deployed a new SQL Server 2005 production server 6 weeks ago. This
> server has 8 GBmemoryand is configured with AWE enabled, 6656 MB max
> servermemoryand /3GB switch.
[...]
> Every 30 seconds these messages were logged in the error log:AppDomain29 (master.dbo[runtime].28) ismarkedforunloadduetomemorypressure.AppDomain29 (master.dbo[runtime].28) unloaded.AppDomain30 (master.dbo[runtime].29) created.
I am having something similar happen.
I found this, which doesn't directly apply to me (we're on SP2, so it
should be fixed), but we are getting those messages as well.
http://support.microsoft.com/kb/917271
However, at least one other person is having this happen:
http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/78717b6a0452847a/ad371baa9fa12a4d?hl=en&lnk=st&q=AppDomain+is+marked+for+unload+due+to+memory+pressure.#ad371baa9fa12a4d
It says user defined datatypes and CLR, and mine has a specific
database name, so that's where I'm looking first. Will post more as I
find it.|||On Dec 4, 3:03 pm, bour...@.gmail.com wrote:
> On Nov 14, 9:39 am, vlad <vesmu...@.yahoo.com> wrote:
> > We deployed a new SQL Server 2005 production server 6 weeks ago. This
> > server has 8 GBmemoryand is configured with AWE enabled, 6656 MB max
> > servermemoryand /3GB switch.
> [...]
> > Every 30 seconds these messages were logged in the error log:AppDomain29 (master.dbo[runtime].28) ismarkedforunloadduetomemorypressure.AppDomain29 (master.dbo[runtime].28) unloaded.AppDomain30 (master.dbo[runtime].29) created.
> I am having something similar happen.
> I found this, which doesn't directly apply to me (we're on SP2, so it
> should be fixed), but we are getting those messages as well.http://support.microsoft.com/kb/917271
> However, at least one other person is having this happen:http://groups.google.com/group/microsoft.public.sqlserver.server/brow...
> It says user defined datatypes and CLR, and mine has a specific
> database name, so that's where I'm looking first. Will post more as I
> find it.
We are also running SP2. The message is related to master since the
CLR assembly is created in master. It happens once in 3 days now
during the pick hours. DBCC FREESYSTEMCACHE doesn't help at all, only
reboot.
Opened a ticket with Microsoft but they have no idea what's happening.
Asked me to run PSSDiag and send a result to them.
These are the performance counters related to memory when the issue
occurs:
Memory: Available Bytes: 602,260,000
Memory: Pages/sec: 0
Process: Working Set Total: 778,264,576
Process: Working Set SQL Server: 262,144,000
SQL Server: Buffer Manager: Buffer Cache Hit Ratio: 99.851
SQL Server: Buffer Manager: Total Pages: 851,968
SQL Server: Memory Manager: Total Server Memory (KB): 6,815,744
MEMORYCLERK_SQLCLR (Total) KB
--- --
VM Reserved 133760
VM Committed 19572
There is no any other processes running on the server at the time.
Don't see any memory pressure.
This is really frustrating since it was running on a less powerful
hardware with 3GB RAM with SQL Server 2000 just 2 months ago with no
issues.
I really need help with this one.
Thanks,
Vlad
App_Data new DB fails
Hello,
I'm trying to create a new SQL Express database in VWD, and I get the error: Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
What is this error all about? I don't understand it.
Thanks.
The db when added in VS has no owner and is somehow bound to the profile. So many things can go wrong with that, so instead of guessing, wipe it out and let the IDE recreate it.
This blog saved me days of heartache. Unfortunately, I still wasted time till I came across it.
http://www.sqljunkies.com/WebLog/ktegels/archive/2005/11/15/17401.aspx
1. Disconnect all dbs, close down the IDE, close down SSMS(if any) on your machine.
2. Stop all services and processes related to sql server.
3. Rename(safer than deleting) the whole folder:
c:\Documents and Settings\[user]\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS
4.restart the IDE/SSE.
5. this song-n-dance may not work the first time. Try more than once.
I am really disappointed at the flaky architecture of SSE and have stopped using it since.
HTH!
Subscribe to:
Posts (Atom)