Tuesday, March 27, 2012
Does SQL Server 7 has anything to do with JVM?
According to: http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodS, SQLServer7 is supported until Dec 31, 2005. I do not understand why Microsoft is still supporting it but us developers can not get a copy!Hi,
The http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodS states
that SQL 7 will be supported till Dec 2005, but the availibility of SQL 7
was only till March 99.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.|||My understanding March 1, 1999 is the General Availibility (GA) date, or the first shipping date, not the last day it will be shipped.|||Hi,
I am sorry, it was my mistake.
Your understanding is correct.
The Softwares like (SQL 7) is still supported to benefit the existing users
of it.
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
Does SQL Server 7 has anything to do with JVM?
According to: http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodS, SQLServer7 is supported until Dec 31, 2005. I do not understand why Microsoft is still supporting it but us developers can not get a copy!
Hi,
The http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodS states
that SQL 7 will be supported till Dec 2005, but the availibility of SQL 7
was only till March 99.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
|||My understanding March 1, 1999 is the General Availibility (GA) date, or the first shipping date, not the last day it will be shipped.
|||Hi,
I am sorry, it was my mistake.
Your understanding is correct.
The Softwares like (SQL 7) is still supported to benefit the existing users
of it.
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
Does SQL Server 7 has anything to do with JVM?
py of SQL Server 7 from Microsoft is because the "Java settlement". Does any
one know why?
According to: http://support.microsoft.com/default.aspx?id=fh;[ln];lifep
rodS, SQLServer7 is supported until Dec 31, 2005. I do not understand why Mi
crosoft is still supporting it but us developers can not get a copy!Hi,
The http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodS state
s
that SQL 7 will be supported till Dec 2005, but the availibility of SQL 7
was only till March 99.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.|||My understanding March 1, 1999 is the General Availibility (GA) date, or the
first shipping date, not the last day it will be shipped.|||Hi,
I am sorry, it was my mistake.
Your understanding is correct.
The Softwares like (SQL 7) is still supported to benefit the existing users
of it.
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
Sunday, March 11, 2012
Does Link in Subscription Point to Live or Snapshot?
This should be an easy one...
You get an email that contains a link to a report. The email was sent automatically as part of a subscription.
Does that link point to a snapshot that was taken when the report was run, or does clicking the link cause the report to re-run altogether?
Thanks,
Dan
Hello Dan,
The link will always point to the current report. For instance, if you have an email subscription that goes out at 6am daily, and today at 8am, you open the report from the link in today's and yesterday's email, they both will take you to the most current report.
As for if it will be re-run, that depends on how you have the execution on the report setup. Whether it is 'Always run this report with the most recent data' or 'Render this report from a report execution snapshot' will determine this.
Hope this helps.
Jarret
|||Hi Jarret,
That's exactly what I needed to know.
Thanks so much!
Dan
Wednesday, March 7, 2012
Does anyone know what this means? Anyone?
get this when trying to send an email subscription or a file-share
subscription. Running the service as a domain account and made the account a
member of the WAA group.I should probably mention that I love the "there is more information in the
log file" message that you can find....you guessed it...in the log file.
"chicagoclone" wrote:
> AuthzInitializeContextFromSid: Win32 error: 234
> get this when trying to send an email subscription or a file-share
> subscription. Running the service as a domain account and made the account a
> member of the WAA group.|||In fact, I read the log file, it said "there is more information in the log
file".
so I checked the log file, and it said "there is more information in the log
file".
so I checked the log file, and it said "there is more information in the log
file".
so I checked the log file, and it said "there is more information in the log
file".
so I checked the log file, and it said "there is more information in the log
file".
so I checked the log file, and it said "there is more information in the log
file".
so I checked the log file, and it said "there is more information in the log
file".
so I checked the log file, and it said "there is more information in the log
file".
so I checked the log file, and it said "there is more information in the log
file".
so I checked the log file, and it said "there is more information in the log
file".
I eventually got out of this endless loop after about 16 hours of
recursively checking the log file.
"chicagoclone" wrote:
> AuthzInitializeContextFromSid: Win32 error: 234
> get this when trying to send an email subscription or a file-share
> subscription. Running the service as a domain account and made the account a
> member of the WAA group.
Sunday, February 26, 2012
Does adding a new column cause entire subscription to reinitialize?
Some hopefully simple questions for the replication experts!
SQL Server 2000, transactional replication, one publisher, one
subscriber.
I have added a column to an article on the publisher and the publisher
is already published. Initially I tried to do this as follows:
sp_repladdcolumn@.source_object = 'tblA',
@.column = 'NewField',
@.typetext = 'int NULL',
@.publication_to_add = 'MyPublication',
@.force_reinit_subscription = 0
but this gave me an error message:
"Error 21381. Cannot add (drop) column to table 'tblA' because the
table belongs to publication(s) with an active updatable subscription.
Set @.force_reinit_subscription to 1 to force reinitialization"
I then re-ran the above with @.force_reinit_subscription=1. The command
worked and returned the message "subscription(s) reinitliazed" but the
new column hasn't appeared on the subscriber.
My questions are as follows:
1 - Do I have to re-run the Snapshot Agent?
2 - If I do re-run the Snapshot Agent, will it reinitialize all other
tables (and their data) or will it just add the new column?
3 - Is there a way I can view the reinitialization commands that are
queued at the publisher to see whether the queued command is to add the
new column or whether it is to reinitialize everything?
Thanks very much!
Pawel
For information: the snapshot agent ran in the evening. The snapshot
agent copied across the new field ALONG WITH all tables related to
'tblA', so it's just as well that I didn't kick it off manually during
the day.
I would still like to know if there is a way to view the commands which
the snapshot agent is due to execute. Does anyone know?
Thanks
Pawel
Pawel wrote:
> Hello,
> Some hopefully simple questions for the replication experts!
> SQL Server 2000, transactional replication, one publisher, one
> subscriber.
> I have added a column to an article on the publisher and the publisher
> is already published. Initially I tried to do this as follows:
> sp_repladdcolumn@.source_object = 'tblA',
> @.column = 'NewField',
> @.typetext = 'int NULL',
> @.publication_to_add = 'MyPublication',
> @.force_reinit_subscription = 0
> but this gave me an error message:
> "Error 21381. Cannot add (drop) column to table 'tblA' because the
> table belongs to publication(s) with an active updatable subscription.
> Set @.force_reinit_subscription to 1 to force reinitialization"
> I then re-ran the above with @.force_reinit_subscription=1. The command
> worked and returned the message "subscription(s) reinitliazed" but the
> new column hasn't appeared on the subscriber.
> My questions are as follows:
> 1 - Do I have to re-run the Snapshot Agent?
> 2 - If I do re-run the Snapshot Agent, will it reinitialize all other
> tables (and their data) or will it just add the new column?
> 3 - Is there a way I can view the reinitialization commands that are
> queued at the publisher to see whether the queued command is to add the
> new column or whether it is to reinitialize everything?
> Thanks very much!
> Pawel
|||Pawel,
as your test shows, if you are specifying @.force_reinit_subscription=1, the
snapshot will contain everything and if not, it won't. To see the commands
that the snapshot agent runs you can use sp_browsereplcmds. Also you can
look in the distribution working folder to see the actual files.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Just to clarify, I don't think the snapshot contained everything. It
looks like it only contained the tables which have a relationship with
'tblA', not all the tables in the published database.
Thanks for the note about sp_browsereplcmds.
Pawel
Paul Ibison wrote:
> Pawel,
> as your test shows, if you are specifying @.force_reinit_subscription=1, the
> snapshot will contain everything and if not, it won't. To see the commands
> that the snapshot agent runs you can use sp_browsereplcmds. Also you can
> look in the distribution working folder to see the actual files.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)